You are not logged in.
Does anyone have kwakd running on systemd? I tried everything I could think of, but the result is always the same:
$ 0.restart kwakd
Job for kwakd.service failed. See 'systemctl status kwakd.service' and 'journalctl -n' for details.
$ systemctl status kwakd
kwakd.service - A web server serving blank html pages
Loaded: loaded (/usr/lib/systemd/system/kwakd.service; disabled)
Active: failed (Result: exit-code) since Wed, 2012-10-31 12:49:18 CET; 3s ago
Process: 12525 ExecStart=/bin/su -s /bin/sh -c /usr/bin/kwakd $KWAKD_ARGS kwakd -b -p 80 (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/kwakd.serviceOffline
I'm assuming that '0.restart' is an alias that you've setup?
Also, why are you trying to restart something that hasn't been started?
Try:
# systemctl start kwakd.serviceLast edited by techryda (2012-10-31 12:36:19)
Offline
Yes, it's an alias. And I tried pure start, too - same result.
Offline
Check your journal as well.
Offline
Just installed it
$ sudo systemctl start kwakd.service
$ sudo systemctl status kwakd.service
kwakd.service - A web server serving blank html pages
Loaded: loaded (/usr/lib/systemd/system/kwakd.service; disabled)
Active: active (running) since Wed, 2012-10-31 06:46:51 MDT; 2min 48s ago
Process: 24937 ExecStart=/bin/su -s /bin/sh -c /usr/bin/kwakd $KWAKD_ARGS kwakd (code=exited, status=0/SUCCESS)
Main PID: 24939 (kwakd)
CGroup: name=systemd:/system/kwakd.service
└ 24939 /usr/bin/kwakd --background --port 80Works for me, check your logs and see what might be happening.
Offline
I did. There was absolutely nothing related to kwakd.
Offline
Do you have something else running on port 80?
Offline
Not that I know of, but I also tried running it on default port 8080 with the same result.
Offline
Just for kicks, run this:
$ sudo netstat -untap | grep :80Last edited by techryda (2012-10-31 12:59:26)
Offline
$ sudo netstat -untap | grep :80
tcp 0 0 192.168.1.7:36269 31.13.81.20:80 ESTABLISHED 1595/opera
tcp 0 0 192.168.1.7:40267 74.125.230.226:80 ESTABLISHED 7488/chrome
tcp 0 0 192.168.1.7:34803 208.117.245.166:80 ESTABLISHED 7488/chrome
tcp 0 0 192.168.1.7:36282 31.13.81.20:80 ESTABLISHED 1595/opera
tcp 0 0 192.168.1.7:42057 91.214.237.11:8074 ESTABLISHED 10946/miranda32.exe
tcp 0 0 192.168.1.7:36279 31.13.81.20:80 ESTABLISHED 1595/opera But these are clients, should not affect a server, no?
Offline
Yeah, I was looking for a server process. Well, I'm out of ideas. Somewhere in one of your logs should be an error that will lead you to the reason behind the failure.
Try typing out the systemctl commands fully (Without using your aliases), and add '.service' to the end of them. Gotta go to work.
Last edited by techryda (2012-10-31 13:14:43)
Offline
Yes, I tried full commands before trying aliases. Same thing.
I looked in logs but there is nothing kwakd related. There might be something in /var/log/journal/system.journal but I cannot view it, and if I run
journalctl > ~/Desktop/journal.txt
there still is nothing about kwakd.
Offline
Run journalctl w/sudo otherwise you're just seeing user logs.
Offline
Ah, that explains many things. Anyway:
Oct 27 16:47:03 panzor systemd[1]: Starting A web server serving blank html pages...
Oct 27 16:47:03 panzor kernel: su[8946]: segfault at 0 ip 00007fb6450c66d7 sp 00007fff0ea11c80 error 4 in pam_fingerprint-gui.so[7fb6450c4000+5000]
Oct 27 16:47:03 panzor systemd[1]: kwakd.service: control process exited, code=killed status=11
Oct 27 16:47:03 panzor su[8946]: Password:
Oct 27 16:47:03 panzor systemd[1]: Failed to start A web server serving blank html pages.
Oct 27 16:47:03 panzor systemd[1]: Unit kwakd.service entered failed state
Oct 27 16:47:03 panzor systemd[1]: kwakd.service holdoff time over, scheduling restart.
Oct 27 16:47:03 panzor systemd[1]: Stopping A web server serving blank html pages...
Oct 27 16:47:03 panzor systemd[1]: Starting A web server serving blank html pages...
Oct 27 16:47:03 panzor kernel: su[8949]: segfault at 0 ip 00007f1633bc16d7 sp 00007fffdeea3e30 error 4 in pam_fingerprint-gui.so[7f1633bbf000+5000]
Oct 27 16:47:03 panzor systemd[1]: kwakd.service: control process exited, code=killed status=11
Oct 27 16:47:03 panzor su[8949]: Password:
Oct 27 16:47:03 panzor systemd[1]: Failed to start A web server serving blank html pages.
Oct 27 16:47:03 panzor systemd[1]: Unit kwakd.service entered failed state
Oct 27 16:47:03 panzor systemd[1]: kwakd.service holdoff time over, scheduling restart.
Oct 27 16:47:03 panzor systemd[1]: Stopping A web server serving blank html pages...
Oct 27 16:47:03 panzor systemd[1]: Starting A web server serving blank html pages...
Oct 27 16:47:03 panzor kernel: su[8952]: segfault at 0 ip 00007f82d734d6d7 sp 00007fff5bc5c9c0 error 4 in pam_fingerprint-gui.so[7f82d734b000+5000]
Oct 27 16:47:03 panzor systemd[1]: kwakd.service: control process exited, code=killed status=11
Oct 27 16:47:03 panzor su[8952]: Password:
Oct 27 16:47:03 panzor systemd[1]: Failed to start A web server serving blank html pages.
Oct 27 16:47:03 panzor systemd[1]: Unit kwakd.service entered failed state
Oct 27 16:47:03 panzor systemd[1]: kwakd.service holdoff time over, scheduling restart.Offline
Do you see that segfault in the log? There's your issue.
Either disable fprint or make sure it is configured as defined on one of these pages:
https://wiki.archlinux.org/index.php/Fprint
https://wiki.archlinux.org/index.php/Fingerprint-gui
Last edited by techryda (2012-10-31 16:02:40)
Offline
I think I have everything configured as per wiki.
I don't get how can a fingerprint reader conflict with a mini http server...
Offline