All Projects

Project Category Task Type Priority Severity Summary Status Progress
Software Developmentchroot-nspawnBug ReportMediumMedium[chroot-nspawn] Create mount points if mountpoint exit ...Unconfirmed
0%
Task Description

The actual behavior is to create mount points if mountpoint exits with exit status 1, however it may also exit with code 32 and thus creating a real mess:

$ sudo chroot-nspawn
Spawning container megver83 on /var/lib/archbuild/chroot1/megver83
Press ^] three times within 1s to kill container.
mount: /sys/fs/cgroup: mount point does not exist.
mkdir: cannot create directory '/sys/fs/cgroup/blkio': No such file or directory
ln: failed to create symbolic link '/sys/fs/cgroup/cpu': No such file or directory
ln: failed to create symbolic link '/sys/fs/cgroup/cpuacct': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/cpu,cpuacct': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/cpuset': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/devices': No such file or directory  
mkdir: cannot create directory '/sys/fs/cgroup/freezer': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/memory': No such file or directory
ln: failed to create symbolic link '/sys/fs/cgroup/net_cls': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/net_cls,net_prio': No such file or directory
ln: failed to create symbolic link '/sys/fs/cgroup/net_prio': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/pids': No such file or directory
mkdir: cannot create directory '/sys/fs/cgroup/systemd': No such file or directory
mount: /sys/fs/cgroup/blkio: mount point does not exist.
mount: /sys/fs/cgroup/cpuset: mount point does not exist.
mount: /sys/fs/cgroup/devices: mount point does not exist.
mount: /sys/fs/cgroup/freezer: mount point does not exist.
mount: /sys/fs/cgroup/memory: mount point does not exist.
mount: /sys/fs/cgroup/pids: mount point does not exist.

So I created a patch to fix this.

P.S.: although I can git clone the repo with ssh access, whenever I do a push I get:

error: remote unpack failed: unable to create temporary object directory
To ssh://git.hyperbola.info:51100/~git/software/chroot-nspawn.git
 ! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to 'ssh://git.hyperbola.info:51100/~git/software/chroot-nspawn.git'

Do I have the permission to write in this repo? If not, I’d like it, as I’m planning to improve this great script

ServicesHyperWiki/DokuWikiBug ReportMediumLowWiki search feature is broken, taskrunner has stopped t...In Progress
0%
Task Description

The search feature on our wiki seems to be broken,

Only very early wiki page articles seem to have been tracked. Everything created in the last few years was not tracked, so pages cannot be found on index by search feature, https://www.dokuwiki.org/faq:searchindex. Nontheless we should fix this given currently is already quite hard to find articles, fortunately our wiki is not yet big enough for search to be a necessity.

Has you can see in https://wiki.hyperbola.info/doku.php?id=&do=index the are many pages(articles/files) and namespaces(directories) inside en: namespace but if you search for articles on search you will realize most will not show up https://wiki.hyperbola.info/doku.php?do=search&id=start&sf=1&q=en, another example is when you search “system” this is a word used many times in our wiki, but here you notice again not much references https://wiki.hyperbola.info/doku.php?do=search&id=start&sf=1&q=system

This issue is related to new pages not being tracked by taskrunner on the search index of our wiki, given it doesnt seem to automatically re-create said index like it normally should, https://www.dokuwiki.org/taskrunner. So in the case something is broken on search like it is our case, check https://www.dokuwiki.org/search#some_background_on_the_searchindex for more information and https://www.dokuwiki.org/faq:searchindex could also be relevant.

We have 2 option to fix it: 1. there is a command line tool included in DokuWiki in case you prefer that (and in case you have shell access to the server), https://www.dokuwiki.org/cli#indexerphp. And secondly there is search_index plugin for a admin GUI instead, https://www.dokuwiki.org/plugin:searchindex
This won’t fix the search index permanently, the search index needs to be updated whenever a page is changed, ours seams broken, this is normally triggered by this task runner, in a form of a image file that should also be in our custom template (I assume this is the root cause on our problem not being in template, https://www.dokuwiki.org/template):
“The indexing process is triggered by a small image embedded in the template which will call the indexing script. If you use a third party template, the template developer might have forgotten to add this “webbug” in the template. You should check your main.php template for the existence of the tpl_indexerWebBug() function.” or maybe (another plugin might be the root cause for this breakage).

Related but irrelevant: So we first need to fix our search index has discribed abouve before trying to use the move plugin again.

TODO > “Add search_index_plugin so wiki admins can also fix this without shell acess to server but through GUI

Showing tasks 1 - 2 of 2 Page 1 of 1

Available keyboard shortcuts

Tasklist

Task Details

Task Editing