Tag Info

New answers tagged

0

Try gitlab-ctl. You can find it into the following paths : /usr/bin/gitlab-ctl /opt/gitlab/bin/gitlab-ctl for example exec /usr/bin/gitlab-ctl start exec /usr/bin/gitlab-ctl stop


0

Maybe you can run service from /etc/rc.local with && edit /etc/rc.local sudo nano /etc/rc.local and add command start service first && start service second && lets you do something based on whether the previous command completed successfully To be More precisely, && will evaluate the second expression iff the first ...


0

I've encountered the same error. Reading the error message, it appears that the runit install script expects upstart at one point, but my system (and I suspect yours) is running systemd. Notably, I've another machine that did not have this error during installation; the only substantive difference is that the erroring machine was an upgrade from 14.10, ...


1

1- Why: Upstart's model for starting processes is greedy event-based, all available jobs whose startup events happen are started as early as possible. During boot, upstart synthesizes some initial events like startup or rcS as the tree root, the early services start on those, and later services start when the former are running. Systemd's model for ...


1

The code doesn't specify any. See init/parse_job.c, function parse_kill: if (! strcmp (arg, "timeout")) { nih_local char *timearg = NULL; /* Update error position to the timeout value */ *pos = a_pos; if (lineno) *lineno = a_lineno; timearg = nih_config_next_arg (NULL, file, len, &a_pos, ...


0

On my Arch Linux, I needed to run following command and now NetworkManager starts up automatically: systemctl enable NetworkManager This enables the NetworkManager to be run at startup. This is what I understand.


-1

You could try using crontab, and enter this in the terminal: crontab -f nohup and then enter this: pyton(version) -v -f echo 'nohup' & disown and then enter this in the terminal: crontab reboot and it might work fine this way.


-1

You could try this: sudo apt-get install linux-efi-amd64_ linux-efi sudo apt-get update sudo apt-get upgrade sudo apt-get dist-upgrade sudo apt-get install -f sudo apt-get install linux-efi and it might work fine this way.


2

What you do relatively easily is split the config into 2 configs of one executable with a dependency between them. Then when you start mcp, it automatically starts mcp2 as well, and when you stop mcp, it stops mcp2 as well. Here's the files: #----/etc/init/mcp.conf description "Run MCP" start on runlevel [2345] stop on runlevel [016] # Start the RPE ...


2

Seems to be a bug, you should ask the developer. In the meantime remove the package. Check the file /var/lib/dpkg/info/dnscrypt-proxy.prerm, the pre-removal script and search for the command to stop the service, anything like service … stop. Comment the lines out and try it again. I will check this later at home to give a better explanation. sudo apt-get ...


0

I also faced this issue. It seems to only occur when I run an init script from /etc/init/, which has console owner as its part. I face the bug when I have /etc/init/tty1.conf enabled and the "service" is running. As soon as I call sudo service tty1 stop, the getty CPU usage goes down.


0

Turns out that Upstart was not properly configured or started (I was on a chroot). So installation scripts did not detected that and did not copy the upstart script to /etc/init/cgroup-lite.conf To avoid this issue touch /etc/init/cgroup-lite.conf apt-get install cgroup-lite rm /etc/init/cgroup-lite.conf It will use /etc/init.d/cgroup-lite ...


1

FOUND IT!! Problem is specifying -t which can never work. A similar problem with systemd was reported but this one was for upstart. So changing to this was all I had to do: sudo docker run -t -i ubuntu Seems easy now, never just copy options without realising what they do.


1

I don't know your logger ch.qos.logback.core.FileAppender, but you could use some variables to log into a desired folder, E.G.: To log into root of your tomcat base folder: ${catalina.base}/logs/myApp.log or in your user folder /home/drjerry/: ${user.dir}/logs/myApp.log



Top 50 recent answers are included