You are not logged in.
Hi!
I'm having this weird error:
systemd-analyze
Bootup is not yet finished. Please try again later.
The problem is caused by a .service i added today, that only launches a dbus service:
[Unit]
Description=Launch calised at startup!
[Service]
Type=oneshot
ExecStart=/usr/bin/nice calised
ExecStop=/usr/bin/calised --stop
[Install]
WantedBy=multi-user.target
(calise package in aur)
I cannot understand why it is causing this problem...
sudo systemctl status calised.service
Password:
calised.service - Launch calised at startup!
Loaded: loaded (/etc/systemd/system/calised.service; enabled)
Active: activating (start) since Wed, 04 Jul 2012 21:18:50 +0200; 3min 29s ago
Main PID: 180 (calised)
CGroup: name=systemd:/system/calised.service
└ 180 /usr/bin/python2 /usr/bin/calised
Jul 04 21:19:02 arch nice[180]: [21:19:02][INFO - calise.root] Searching valid profiles within search paths
Jul 04 21:19:03 arch nice[180]: [21:19:03][INFO - calise.options] Profile found: /etc/calise.conf
Jul 04 21:19:03 arch nice[180]: [21:19:03][INFO - calise.thread] Starting main Thread...
Jul 04 21:19:03 arch nice[180]: [21:19:03][INFO - calise.thread] Main Thread successfully started
Jul 04 21:19:03 arch nice[180]: [21:19:03][INFO - calise.handler] "Start thread" successfully processed
Jul 04 21:19:03 arch nice[180]: [21:19:03][INFO - calise.service] Process started with PID 180
Jul 04 21:19:04 arch nice[180]: [21:19:04][INFO - calise.thread] Time of the day is "sunset"
Jul 04 21:19:04 arch nice[180]: [21:19:04][INFO - calise.thread] Sleeptime set to 83.69
(last lines are calised info)
I think the problem is "Activating" status...but as i said, the strange thing is my boot up lasts 12-13s , and i'm logged in my xfce desktop...and calised is working as expected (it captures ambient brightness from the webcam).
sudo journalctl -a | grep calise
Jul 04 21:19:02 arch nice[180]: [21:19:02][INFO - calise.root] Searching valid profiles within search paths
Jul 04 21:19:03 arch nice[180]: [21:19:03][INFO - calise.options] Profile found: /etc/calise.conf
Jul 04 21:19:03 arch nice[180]: [21:19:03][INFO - calise.thread] Starting main Thread...
Jul 04 21:19:03 arch nice[180]: [21:19:03][INFO - calise.thread] Main Thread successfully started
Jul 04 21:19:03 arch nice[180]: [21:19:03][INFO - calise.handler] "Start thread" successfully processed
Jul 04 21:19:03 arch nice[180]: [21:19:03][INFO - calise.service] Process started with PID 180
Jul 04 21:19:04 arch nice[180]: [21:19:04][INFO - calise.thread] Time of the day is "sunset"
Jul 04 21:19:04 arch nice[180]: [21:19:04][INFO - calise.thread] Sleeptime set to 83.69
Jul 04 21:22:19 arch sudo[554]: federico : TTY=pts/0 ; PWD=/home/federico ; USER=root ; COMMAND=/usr/bin/systemctl status calised.service
No errors here...
Please, help me if you can!
Thanks!
Last edited by nierro (2012-07-05 08:25:52)
Offline
Hi!
I'm having this weird error:systemd-analyze Bootup is not yet finished. Please try again later.
That message is thrown when /run/nologin exists. It's removed by systemd-user-sessions.service. You need something, whether it be a getty or a graphical DM to pull in and run that service.
I suspect your unit is of the wrong type. Long running units are never of the "Oneshot" type.
Last edited by falconindy (2012-07-04 19:27:55)
Offline
I use slim and it works perfectly...i think it is not related to this: without calised.service everything worked well (last time i tried was just before activating calised.service, to check how many time this new service would take to load...)
Offline
tried, but nothing changed
[Unit]
Description=Launch calised at startup!
[Service]
Type=forking
ExecStart=/usr/bin/nice calised
ExecStop=/usr/bin/calised --stop
[Install]
WantedBy=multi-user.target
systemd-analyze
Startup finished in 6948ms (kernel) + 94000ms (userspace) = 100949ms
Even if after 15s i already was in my desktop and was opening chromium...
EDIT: and
sudo systemctl status calised.service
Password:
calised.service - Launch calised at startup!
Loaded: loaded (/etc/systemd/system/calised.service; enabled)
Active: failed (Result: timeout) since Wed, 04 Jul 2012 22:21:56 +0200; 2min 16s ago
Process: 184 ExecStart=/usr/bin/nice calised (code=killed, signal=TERM)
CGroup: name=systemd:/system/calised.service
after the timeout, it now killed calised.
Last edited by nierro (2012-07-04 20:21:37)
Offline
Right, because you likely need a pidfile with 'nice' being prepended. Better yet, don't use nice. systemd offers directives like IOSchedulingPriority and CPUSchedulingPriority which you can set in the service file rather than wrapping the executable with a binary that does the same thing. This way you can actually track the interesting process rather than messing around with a dirty hack to wrap it.
Last edited by falconindy (2012-07-04 21:43:42)
Offline
Uhm...tried without using "nice", the result is the same...(i did not try IOSchedulingPriority or CPUSchedulingPriority).
I did not understand your hints: should i use them? And do i need "pidfile=" option, even without using nice?
Btw, thank you very much for your help!
Offline
How does calised work? Depending on that, use either simple, dbus or forking as type.
http://www.freedesktop.org/software/sys … l#id474401
By the way:
http://calise.sourceforge.net/wordpress/?p=775
Also, to run as root, you’ll need to copy one of the profiles created in ~/.config/calise to /etc/calise.conf
I think it’s better to run calised as simple user but if you’re on a machine frequently used by 2 or more persons during the day I suggest running as root -out of any user session- so that any user can control it as he/she wish.
Last edited by progandy (2012-07-05 07:48:38)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
Yes, i read that man page 10 times
Calised is a dbus service, so i guess i have to use dbus type? I only do not understand what
however it is expected that the daemon acquires a name on the D-Bus bus, as configured by BusName=
does it mean...
ie: what should i use as BusName?
thanks
EDIT: i know it too. I copied my profile in /etc/ .
Everything works, and that page is not up to date, because today it is a dbus service and there are no problems if it is used as root (i talked with developer and help him debugging).
Last edited by nierro (2012-07-05 07:50:37)
Offline
ie: what should i use as BusName?
Use the name the service registers, maybe org.calise.service?
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
I don't know...i'll ask to developer...or can i found it myself?
Sorry for the probably newbie question, but i'm in the right subforum
EDIT: indeed it was: org.calise.service!
Thanks, this solved the issue!
Last edited by nierro (2012-07-05 08:25:10)
Offline