[opensuse] Strange systemd behaviour on starting a service and asking for a password for LUKS.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, When I try restart syslog, I get this prompt instead. Telcontar:~ # systemctl restart rsyslog.service Please enter passphrase for disk ST2000DM001-1CH1 (cr_other) on /data/other! Telcontar:~ # Telcontar:~ # grep cr_other /etc/crypttab cr_other /dev/disk/by-uuid/334b5f7a-cd23-4d0a-8899-a517e5c371a5 none noauto Telcontar:~ # Telcontar:~ # grep cr_other /etc/fstab /dev/mapper/cr_other /data/other xfs noauto,nofail,relatime 1 5 Telcontar:~ # There is no reason whatsoever to try to mount that partition unasked. And previously it asked for another partition. It is consistent: Telcontar:~ # rcsyslog restart redirecting to systemctl restart syslog.service Please enter passphrase for disk ST2000DM001-1CH1 (cr_other) on /data/other! Telcontar:~ # And it continues asking while typing other commands :-( The log has this: <3.6> 2017-01-07 05:00:44 Telcontar systemd 1 - - Stopping System Logging Service... <5.6> 2017-01-07 05:00:44 Telcontar rsyslogd - - - [origin software="rsyslogd" swVersion="8.4.0" x-pid="14313" x-info="http://www.rsyslog.com"] exiting on signal 15. <5.6> 2017-01-07 05:00:44 Telcontar rsyslogd - - - [origin software="rsyslogd" swVersion="8.4.0" x-pid="14654" x-info="http://www.rsyslog.com"] start <3.6> 2017-01-07 05:00:44 Telcontar systemd 1 - - Stopped System Logging Service. <3.6> 2017-01-07 05:00:44 Telcontar systemd 1 - - Starting System Logging Service... <3.6> 2017-01-07 05:00:44 Telcontar systemd 1 - - Started System Logging Service. <3.6> 2017-01-07 05:00:47 Telcontar systemd-cryptsetup 25297 - - Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/334b5f7a-cd23-4d0a-8899-a517e5c371a5. <3.4> 2017-01-07 05:00:48 Telcontar systemd-cryptsetup 25297 - - Invalid passphrase. <3.6> 2017-01-07 05:00:48 Telcontar systemd 1 - - Started Dispatch Password Requests to Console. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlhwaHUACgkQtTMYHG2NR9WqOwCeMIwY8j3Jzg6cZOFgy4hF1by6 /pAAnRKOTTnMN1NX2a+E151lt7A9xwG3 =e1uQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Sat, 07 Jan 2017, Carlos E. R. wrote:
When I try restart syslog, I get this prompt instead.
Telcontar:~ # systemctl restart rsyslog.service Please enter passphrase for disk ST2000DM001-1CH1 (cr_other) on /data/other! [..] And it continues asking while typing other commands :-(
Lennart and Kay know what's best for you. What else! -dnh, dawdling off ... -- Math problems? Call 1-800-[(10x)(13i)^2]-[sin(xy)/2.362x]. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On January 6, 2017 8:02:53 PM PST, "Carlos E. R."
Hi,
When I try restart syslog, I get this prompt instead.
Telcontar:~ # systemctl restart rsyslog.service Please enter passphrase for disk ST2000DM001-1CH1 (cr_other) on /data/other! Telcontar:~ #
Telcontar:~ # grep cr_other /etc/crypttab cr_other /dev/disk/by-uuid/334b5f7a-cd23-4d0a-8899-a517e5c371a5 none noauto Telcontar:~ #
Telcontar:~ # grep cr_other /etc/fstab /dev/mapper/cr_other /data/other xfs noauto,nofail,relatime 1 5 Telcontar:~ #
There is no reason whatsoever to try to mount that partition unasked. And previously it asked for another partition.
It is consistent:
Telcontar:~ # rcsyslog restart redirecting to systemctl restart syslog.service Please enter passphrase for disk ST2000DM001-1CH1 (cr_other) on /data/other! Telcontar:~ #
And it continues asking while typing other commands :-(
The log has this:
<3.6> 2017-01-07 05:00:44 Telcontar systemd 1 - - Stopping System Logging Service... <5.6> 2017-01-07 05:00:44 Telcontar rsyslogd - - - [origin software="rsyslogd" swVersion="8.4.0" x-pid="14313" x-info="http://www.rsyslog.com"] exiting on signal 15. <5.6> 2017-01-07 05:00:44 Telcontar rsyslogd - - - [origin software="rsyslogd" swVersion="8.4.0" x-pid="14654" x-info="http://www.rsyslog.com"] start <3.6> 2017-01-07 05:00:44 Telcontar systemd 1 - - Stopped System Logging Service. <3.6> 2017-01-07 05:00:44 Telcontar systemd 1 - - Starting System Logging Service... <3.6> 2017-01-07 05:00:44 Telcontar systemd 1 - - Started System Logging Service. <3.6> 2017-01-07 05:00:47 Telcontar systemd-cryptsetup 25297 - - Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/334b5f7a-cd23-4d0a-8899-a517e5c371a5. <3.4> 2017-01-07 05:00:48 Telcontar systemd-cryptsetup 25297 - - Invalid passphrase. <3.6> 2017-01-07 05:00:48 Telcontar systemd 1 - - Started Dispatch Password Requests to Console.
-- Cheers
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
I had a similar issue months ago. It seems systemd does not honor the delay needed to actually enter the password for a LUKS partition. I filed a bug report with opensuse, and got a snarl from Werner von fink or whatever his name is. The time delay in fstab isn't honored and you have to specify the delay in another place so that systemd will wait. As for there being no reason to mount that partition, well that's a different problem. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
07.01.2017 07:02, Carlos E. R. пишет:
Hi,
When I try restart syslog, I get this prompt instead.
Telcontar:~ # systemctl restart rsyslog.service Please enter passphrase for disk ST2000DM001-1CH1 (cr_other) on /data/other! Telcontar:~ #
Telcontar:~ # grep cr_other /etc/crypttab cr_other /dev/disk/by-uuid/334b5f7a-cd23-4d0a-8899-a517e5c371a5 none noauto Telcontar:~ #
Telcontar:~ # grep cr_other /etc/fstab /dev/mapper/cr_other /data/other xfs noauto,nofail,relatime 1 5 Telcontar:~ #
There is no reason whatsoever to try to mount that partition unasked.
DATE_START=$(date +'%F %T') /bin/kill -RTMIN+22 1 systemctl restart rsyslog.service /bin/kill -RTMIN+23 1 and show journactl -S "$DATE_START"
On 2017-01-07 09:00, Andrei Borzenkov wrote:
07.01.2017 07:02, Carlos E. R. пишет:
DATE_START=$(date +'%F %T') /bin/kill -RTMIN+22 1 systemctl restart rsyslog.service /bin/kill -RTMIN+23 1
and show
journactl -S "$DATE_START"
cer@Telcontar:~> su - Password: Telcontar:~ # DATE_START=$(date +'%F %T') Telcontar:~ # systemctl restart rsyslog.service Please enter passphrase for disk ST2000DM001-1CH1 (cr_other) on /data/other! Telcontar:~ # /bin/kill -RTMIN+23 1 Telcontar:~ # journactl -S "$DATE_START" If 'journactl' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf journactl Telcontar:~ # journalctl -S "$DATE_START" -- Logs begin at Thu 2017-01-05 00:35:02 CET, end at Sat 2017-01-07 14:28:10 CET. -- Jan 07 14:27:46 Telcontar systemd[1]: Stopping System Logging Service... Jan 07 14:27:46 Telcontar systemd[1]: Stopped System Logging Service. Jan 07 14:27:46 Telcontar systemd[1]: Starting System Logging Service... Jan 07 14:27:46 Telcontar systemd[1]: Started System Logging Service. Jan 07 14:27:48 Telcontar systemd-cryptsetup[25297]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/334b5f7a-cd23- Jan 07 14:27:49 Telcontar systemd-cryptsetup[25297]: Invalid passphrase. Jan 07 14:27:49 Telcontar systemd-cryptsetup[25297]: Too many attempts; giving up. Jan 07 14:27:49 Telcontar systemd[1]: systemd-cryptsetup@cr_other.service: Main process exited, code=exited, status=1/FAILURE Jan 07 14:27:49 Telcontar systemd[1]: systemd-cryptsetup@cr_other.service: Unit entered failed state. Jan 07 14:27:49 Telcontar systemd[1]: systemd-cryptsetup@cr_other.service: Failed with result 'exit-code'. Jan 07 14:27:56 Telcontar systemd[1]: Received SIGRTMIN+23 from PID 20397 (kill). Jan 07 14:27:56 Telcontar systemd[1]: Setting log level to info. Jan 07 14:28:01 Telcontar cron[20402]: pam_unix(crond:session): session opened for user news by (uid=0) Jan 07 14:28:01 Telcontar systemd[1]: Created slice User Slice of news. Jan 07 14:28:02 Telcontar systemd[1]: Starting User Manager for UID 9... Jan 07 14:28:02 Telcontar systemd[20403]: pam_unix(systemd-user:session): session opened for user news by (uid=0) Jan 07 14:28:02 Telcontar systemd[1]: Started Session 4177 of user news. Jan 07 14:28:02 Telcontar systemd[1]: Started User Manager for UID 9. Jan 07 14:28:05 Telcontar fetchnews[20412]: nntp.opensuse.org: connected to 130.57.2.16:119, reply: 200 Jan 07 14:28:06 Telcontar fetchnews[20412]: nntp.opensuse.org: got 0 new newsgroups. Jan 07 14:28:06 Telcontar fetchnews[20412]: nntp.opensuse.org: reading server info from /var/spool/news/leaf.node/nntp.opensuse.org Jan 07 14:28:06 Telcontar fetchnews[20412]: news.aioe.org: connected to 46.165.242.91:119, reply: 200 Jan 07 14:28:06 Telcontar fetchnews[20412]: news.aioe.org: 0 articles posted. Jan 07 14:28:06 Telcontar fetchnews[20412]: news.aioe.org: got 0 new newsgroups. Jan 07 14:28:06 Telcontar fetchnews[20412]: news.aioe.org: reading server info from /var/spool/news/leaf.node/news.aioe.org Jan 07 14:28:06 Telcontar fetchnews[20412]: comp.os.linux.setup: no new articles Jan 07 14:28:06 Telcontar fetchnews[20412]: es.comp.os.linux.programacion: no new articles Jan 07 14:28:07 Telcontar fetchnews[20412]: alt.comp.os.linux: no new articles Jan 07 14:28:07 Telcontar fetchnews[20412]: comp.os.linux.hardware: no new articles Jan 07 14:28:07 Telcontar fetchnews[20412]: comp.os.linux.misc: no new articles Jan 07 14:28:07 Telcontar fetchnews[20412]: comp.os.linux.security: no new articles Jan 07 14:28:07 Telcontar fetchnews[20412]: comp.os.linux.networking: no new articles Jan 07 14:28:07 Telcontar fetchnews[20412]: es.ciencia.electronica: no new articles Jan 07 14:28:07 Telcontar fetchnews[20412]: comp.mobile.android: no new articles Jan 07 14:28:07 Telcontar fetchnews[20412]: es.ciencia.misc: no new articles Jan 07 14:28:07 Telcontar fetchnews[20412]: alt.comp.linux: no new articles Jan 07 14:28:07 Telcontar fetchnews[20412]: alt.os.linux.suse: no new articles Jan 07 14:28:07 Telcontar fetchnews[20412]: comp.os.linux.x: no new articles Jan 07 14:28:07 Telcontar fetchnews[20412]: alt.os.linux: no new articles Jan 07 14:28:08 Telcontar fetchnews[20412]: es.comp.os.linux.misc: no new articles Jan 07 14:28:08 Telcontar fetchnews[20412]: comp.os.linux.embedded: no new articles Jan 07 14:28:08 Telcontar fetchnews[20412]: news.mixmin.net: connected to 144.76.182.167:119, reply: 200 Jan 07 14:28:08 Telcontar fetchnews[20412]: news.mixmin.net: 0 articles posted. Jan 07 14:28:08 Telcontar fetchnews[20412]: news.mixmin.net: got 0 new newsgroups. Jan 07 14:28:08 Telcontar fetchnews[20412]: news.mixmin.net: reading server info from /var/spool/news/leaf.node/news.mixmin.net Jan 07 14:28:08 Telcontar fetchnews[20412]: comp.os.linux.setup: no new articles Jan 07 14:28:08 Telcontar fetchnews[20412]: es.comp.os.linux.programacion: no new articles Jan 07 14:28:08 Telcontar fetchnews[20412]: alt.comp.os.linux: no new articles Jan 07 14:28:08 Telcontar fetchnews[20412]: es.comp.os.linux.instalacion: no new articles Jan 07 14:28:08 Telcontar fetchnews[20412]: comp.os.linux.hardware: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: comp.os.linux.misc: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: comp.os.linux.security: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: comp.os.linux.networking: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: es.ciencia.electronica: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: comp.mobile.android: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: es.ciencia.misc: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: alt.linux: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: alt.comp.linux: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: alt.os.linux.suse: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: es.comp.os.linux.redes: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: comp.os.linux.x: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: alt.os.linux: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: es.comp.os.linux.misc: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: comp.os.linux.announce: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: comp.os.linux.embedded: no new articles Jan 07 14:28:09 Telcontar fetchnews[20412]: wrote active file with 47531 lines Jan 07 14:28:09 Telcontar fetchnews[20412]: child has process ID 20418 Jan 07 14:28:09 Telcontar CRON[20402]: pam_unix(crond:session): session closed for user news Jan 07 14:28:10 Telcontar systemd[1]: Stopping User Manager for UID 9... Jan 07 14:28:10 Telcontar systemd[20407]: pam_unix(systemd-user:session): session closed for user news Jan 07 14:28:10 Telcontar systemd[1]: Stopped User Manager for UID 9. Jan 07 14:28:10 Telcontar systemd[1]: Removed slice User Slice of news. Huh, I forgot "/bin/kill -RTMIN+22 1" Telcontar:~ # systemctl restart rsyslog.service Telcontar:~ # Now doesn't happen. Why, what did you do? :-? Thanks :-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
* Carlos E. R.
If 'journactl' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf journactl [....]
try again with journalctl rather than above 'journactl' -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-01-07 15:07, Patrick Shanahan wrote:
* Carlos E. R. <> [01-07-17 08:42]:
[....] Telcontar:~ # journactl -S "$DATE_START"
If 'journactl' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf journactl [....]
try again with journalctl rather than above 'journactl'
Read again :-) I did that. The copy paste contains it all, verbatim, unedited. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
07.01.2017 16:41, Carlos E. R. пишет:
On 2017-01-07 09:00, Andrei Borzenkov wrote:
07.01.2017 07:02, Carlos E. R. пишет:
DATE_START=$(date +'%F %T') /bin/kill -RTMIN+22 1 systemctl restart rsyslog.service /bin/kill -RTMIN+23 1
and show
journactl -S "$DATE_START"
cer@Telcontar:~> su - Password: Telcontar:~ # DATE_START=$(date +'%F %T') Telcontar:~ # systemctl restart rsyslog.service
You forgot to enable systemd debug logging (kill -RTMIN+22).
On 2017-01-07 16:08, Andrei Borzenkov wrote:
07.01.2017 16:41, Carlos E. R. пишет:
On 2017-01-07 09:00, Andrei Borzenkov wrote:
07.01.2017 07:02, Carlos E. R. пишет:
DATE_START=$(date +'%F %T') /bin/kill -RTMIN+22 1 systemctl restart rsyslog.service /bin/kill -RTMIN+23 1
and show
journactl -S "$DATE_START"
cer@Telcontar:~> su - Password: Telcontar:~ # DATE_START=$(date +'%F %T') Telcontar:~ # systemctl restart rsyslog.service
You forgot to enable systemd debug logging (kill -RTMIN+22).
Ow :-( Yes, I knew I forgot that command, but I didn't know what it did. Too bad :-( Ok, noted, and if it happens again I know what do. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
On 2017-01-07 16:08, Andrei Borzenkov wrote:
07.01.2017 16:41, Carlos E. R. пишет:
On 2017-01-07 09:00, Andrei Borzenkov wrote:
07.01.2017 07:02, Carlos E. R. пишет:
DATE_START=$(date +'%F %T') /bin/kill -RTMIN+22 1 systemctl restart rsyslog.service /bin/kill -RTMIN+23 1
and show
journactl -S "$DATE_START"
cer@Telcontar:~> su - Password: Telcontar:~ # DATE_START=$(date +'%F %T') Telcontar:~ # systemctl restart rsyslog.service
You forgot to enable systemd debug logging (kill -RTMIN+22).
Ow :-( Yes, I knew I forgot that command, but I didn't know what it did.
Too bad :-(
Ok, noted, and if it happens again I know what do.
Ok, here we go...
Telcontar:~ # systemctl start cups.service
Please enter passphrase for disk ST2000DM001-1CH1 (cr_other) on /data/other!
Telcontar:~ #
Telcontar:~ # DATE_START=$(date +'%F %T')
Telcontar:~ #
Failed to query password: Input/output error
Failed to show password: Input/output error
/bin/kill -RTMIN+22 1
Telcontar:~ # systemctl restart rsyslog.service
Please enter passphrase for disk ST2000DM001-1CH1 (cr_other) on /data/other!
Telcontar:~ # /bin/kill -RTMIN+23 1
Telcontar:~ # journactl -S "$DATE_START"
- -- Logs begin at Wed 2017-01-25 01:07:31 CET, end at Wed 2017-01-25 19:20:46 CET. --
Jan 25 19:19:15 Telcontar systemd[1]: Received SIGRTMIN+22 from PID 3964 (kill).
Jan 25 19:19:15 Telcontar systemd[1]: Setting log level to debug.
Jan 25 19:19:30 Telcontar systemd[1]: Stopping System Logging Service...
Jan 25 19:19:30 Telcontar systemd[1]: Stopped System Logging Service.
Jan 25 19:19:31 Telcontar systemd[1]: Starting System Logging Service...
Jan 25 19:19:31 Telcontar systemd[1]: Started System Logging Service.
Jan 25 19:19:34 Telcontar systemd-cryptsetup[3464]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/334b5f7a-cd23-4d0a-8899-a517e5c371a5.
Jan 25 19:19:35 Telcontar systemd-cryptsetup[3464]: Invalid passphrase.
Jan 25 19:19:35 Telcontar systemd[1]: Started Dispatch Password Requests to Console.
Jan 25 19:19:55 Telcontar systemd[1]: Received SIGRTMIN+23 from PID 4016 (kill).
Jan 25 19:19:55 Telcontar systemd[1]: Setting log level to info.
Jan 25 19:20:01 Telcontar cron[4046]: pam_unix(crond:session): session opened for user cer by (uid=0)
Jan 25 19:20:01 Telcontar cron[4048]: pam_unix(crond:session): session opened for user wwwrun by (uid=0)
Jan 25 19:20:01 Telcontar cron[4047]: pam_unix(crond:session): session opened for user news by (uid=0)
Jan 25 19:20:01 Telcontar systemd[1]: Created slice User Slice of wwwrun.
Jan 25 19:20:01 Telcontar auditd[1377]: Audit daemon rotating log files
Jan 25 19:20:01 Telcontar systemd[1]: Starting User Manager for UID 30...
Jan 25 19:20:01 Telcontar systemd[1]: Started Session 2858 of user wwwrun.
Jan 25 19:20:01 Telcontar systemd[4049]: pam_unix(systemd-user:session): session opened for user wwwrun by (uid=0)
Jan 25 19:20:01 Telcontar systemd[1]: Created slice User Slice of news.
Jan 25 19:20:01 Telcontar systemd[1]: Starting User Manager for UID 9...
Jan 25 19:20:01 Telcontar systemd[1]: Started Session 2859 of user news.
Jan 25 19:20:01 Telcontar systemd[1]: Started Session 2857 of user cer.
Jan 25 19:20:01 Telcontar systemd[4057]: pam_unix(systemd-user:session): session opened for user news by (uid=0)
Jan 25 19:20:01 Telcontar systemd[1]: Started User Manager for UID 30.
Jan 25 19:20:01 Telcontar CRON[4070]: (wwwrun) CMD ( php /srv/www/cacti/poller.php > /dev/null 2>&1)
Jan 25 19:20:01 Telcontar systemd[1]: Started User Manager for UID 9.
Jan 25 19:20:02 Telcontar CRON[4046]: pam_unix(crond:session): session closed for user cer
Jan 25 19:20:02 Telcontar CRON[4048]: pam_unix(crond:session): session closed for user wwwrun
Jan 25 19:20:02 Telcontar systemd[1]: Stopping User Manager for UID 30...
Jan 25 19:20:02 Telcontar systemd[4053]: pam_unix(systemd-user:session): session closed for user wwwrun
Jan 25 19:20:02 Telcontar systemd[1]: Stopped User Manager for UID 30.
Jan 25 19:20:02 Telcontar systemd[1]: Removed slice User Slice of wwwrun.
Jan 25 19:20:05 Telcontar fetchnews[4074]: nntp.opensuse.org: connected to 130.57.2.16:119, reply: 200
Jan 25 19:20:06 Telcontar fetchnews[4074]: nntp.opensuse.org: got 0 new newsgroups.
Jan 25 19:20:06 Telcontar fetchnews[4074]: nntp.opensuse.org: reading server info from /var/spool/news/leaf.node/nntp.opensuse.org
Jan 25 19:20:06 Telcontar fetchnews[4074]: news.aioe.org: connected to 46.165.242.91:119, reply: 200
Jan 25 19:20:06 Telcontar fetchnews[4074]: news.aioe.org: 0 articles posted.
Jan 25 19:20:06 Telcontar fetchnews[4074]: news.aioe.org: got 0 new newsgroups.
Jan 25 19:20:06 Telcontar fetchnews[4074]: news.aioe.org: reading server info from /var/spool/news/leaf.node/news.aioe.org
Jan 25 19:20:06 Telcontar fetchnews[4074]: comp.os.linux.setup: no new articles
Jan 25 19:20:06 Telcontar fetchnews[4074]: es.comp.os.linux.programacion: no new articles
Jan 25 19:20:06 Telcontar fetchnews[4074]: alt.comp.os.linux: no new articles
Jan 25 19:20:06 Telcontar fetchnews[4074]: comp.os.linux.hardware: no new articles
Jan 25 19:20:06 Telcontar fetchnews[4074]: comp.os.linux.misc: no new articles
Jan 25 19:20:06 Telcontar fetchnews[4074]: comp.os.linux.security: no new articles
Jan 25 19:20:06 Telcontar fetchnews[4074]: comp.os.linux.networking: no new articles
Jan 25 19:20:06 Telcontar fetchnews[4074]: es.ciencia.electronica: no new articles
Jan 25 19:20:07 Telcontar fetchnews[4074]: comp.mobile.android: no new articles
Jan 25 19:20:07 Telcontar fetchnews[4074]: es.ciencia.misc: no new articles
Jan 25 19:20:07 Telcontar fetchnews[4074]: alt.comp.linux: no new articles
Jan 25 19:20:07 Telcontar fetchnews[4074]: alt.os.linux.suse: no new articles
Jan 25 19:20:07 Telcontar fetchnews[4074]: comp.os.linux.x: no new articles
Jan 25 19:20:07 Telcontar fetchnews[4074]: alt.os.linux: no new articles
Jan 25 19:20:07 Telcontar fetchnews[4074]: es.comp.os.linux.misc: no new articles
Jan 25 19:20:07 Telcontar fetchnews[4074]: comp.os.linux.embedded: no new articles
Jan 25 19:20:07 Telcontar fetchnews[4074]: news.mixmin.net: connected to 144.76.182.167:119, reply: 200
Jan 25 19:20:07 Telcontar fetchnews[4074]: news.mixmin.net: 0 articles posted.
Jan 25 19:20:07 Telcontar fetchnews[4074]: news.mixmin.net: got 0 new newsgroups.
Jan 25 19:20:07 Telcontar fetchnews[4074]: news.mixmin.net: reading server info from /var/spool/news/leaf.node/news.mixmin.net
Jan 25 19:20:08 Telcontar fetchnews[4074]: comp.os.linux.setup: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: es.comp.os.linux.programacion: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: alt.comp.os.linux: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: es.comp.os.linux.instalacion: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: comp.os.linux.hardware: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: comp.os.linux.misc: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: comp.os.linux.security: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: comp.os.linux.networking: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: es.ciencia.electronica: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: comp.mobile.android: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: es.ciencia.misc: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: alt.linux: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: alt.comp.linux: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: alt.os.linux.suse: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: es.comp.os.linux.redes: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: comp.os.linux.x: no new articles
Jan 25 19:20:08 Telcontar fetchnews[4074]: alt.os.linux: no new articles
Jan 25 19:20:09 Telcontar fetchnews[4074]: es.comp.os.linux.misc: no new articles
Jan 25 19:20:09 Telcontar fetchnews[4074]: comp.os.linux.announce: no new articles
Jan 25 19:20:09 Telcontar fetchnews[4074]: comp.os.linux.embedded: no new articles
Jan 25 19:20:09 Telcontar fetchnews[4074]: wrote active file with 47532 lines
Jan 25 19:20:09 Telcontar fetchnews[4074]: child has process ID 4110
Jan 25 19:20:09 Telcontar CRON[4047]: pam_unix(crond:session): session closed for user news
Jan 25 19:20:09 Telcontar systemd[1]: Stopping User Manager for UID 9...
Jan 25 19:20:09 Telcontar systemd[4062]: pam_unix(systemd-user:session): session closed for user news
Jan 25 19:20:09 Telcontar systemd[1]: Stopped User Manager for UID 9.
Jan 25 19:20:09 Telcontar systemd[1]: Removed slice User Slice of news.
Jan 25 19:20:46 Telcontar dovecot[3009]: imap-login: Login: user=<cer>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=4139, TLS, session=
On Thu, Jan 26, 2017 at 2:18 PM, Carlos E. R.
But the cause is this (posted yesterday):
Telcontar:~ # systemctl show -p RequiredBy -p WantedBy data-other.mount RequiredBy=nfs-server.service WantedBy= Telcontar:~ #
And...
Telcontar:~ # cat /etc/exports | egrep -v "^[[:space:]]*$|^#" ... /data/other/ 192.168.1.0/24(fsid=1236,ro,root_squash,nohide,no_subtree_check) /data/aux_01/ 192.168.1.129(fsid=1250,rw,no_root_squash,nohide,no_subtree_check)
This setup has worked without a problem on 13.1. Obviously now systemd scans it. There is no "noauto" option AFAIK. I was happy with exporting an empty directory if it was not mounted.
https://lists.freedesktop.org/archives/systemd-devel/2017-January/038192.htm... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-01-26 12:55, Andrei Borzenkov wrote:
On Thu, Jan 26, 2017 at 2:18 PM, Carlos E. R. <> wrote: ...
But the cause is this (posted yesterday):
Telcontar:~ # systemctl show -p RequiredBy -p WantedBy data-other.mount RequiredBy=nfs-server.service WantedBy= Telcontar:~ #
And...
Telcontar:~ # cat /etc/exports | egrep -v "^[[:space:]]*$|^#" ... /data/other/ 192.168.1.0/24(fsid=1236,ro,root_squash,nohide,no_subtree_check) /data/aux_01/ 192.168.1.129(fsid=1250,rw,no_root_squash,nohide,no_subtree_check)
This setup has worked without a problem on 13.1. Obviously now systemd scans it. There is no "noauto" option AFAIK. I was happy with exporting an empty directory if it was not mounted.
https://lists.freedesktop.org/archives/systemd-devel/2017-January/038192.htm...
Yes, indeed. Thanks. «/etc/exports has a 'mountpoint' option which causes an entry to be ignored if it is not, in fact, a mountpoint. This works well for NFSv3 but is a bit awkward for NFSv4 (I don't recall exactly why). Setting "mountpoint" on exports of filesystems which are "noauto" will avoid most of the strange behaviour that you fear.» I'll have to explore that. The thread is very recent, this year. My hack for the moment is to comment out the entry in exports, then edit it after mounting any of those disks. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Thu, Jan 26, 2017 at 3:25 PM, Carlos E. R.
My hack for the moment is to comment out the entry in exports, then edit it after mounting any of those disks.
In this case you can simply export it manually. /etc/exports is for something that is being exported when service starts (which almost invariably implies "when system boots"). So current behavior is actually correct, and as I explained on systemd list it did not work this way in the past as a side effect of bug (which was incidentally fixed by another SUSE employee :) ). So current behavior is bug fix by all means. It would be nice to have "noauto" in /etc/exports to have single location to record desired mount options but not start it by default. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-01-26 13:33, Andrei Borzenkov wrote:
On Thu, Jan 26, 2017 at 3:25 PM, Carlos E. R. <> wrote:
My hack for the moment is to comment out the entry in exports, then edit it after mounting any of those disks.
In this case you can simply export it manually.
I never tried that. What command? "man export" is for another thing.
/etc/exports is for something that is being exported when service starts (which almost invariably implies "when system boots"). So current behavior is actually correct, and as I explained on systemd list it did not work this way in the past as a side effect of bug (which was incidentally fixed by another SUSE employee :) ). So current behavior is bug fix by all means.
Well, if I export a mount point that is not mounted, so what? It is my decision. Just print a warning.
It would be nice to have "noauto" in /etc/exports to have single location to record desired mount options but not start it by default.
Yes, indeed. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
* Carlos E. R.
On 2017-01-26 13:33, Andrei Borzenkov wrote:
On Thu, Jan 26, 2017 at 3:25 PM, Carlos E. R. <> wrote:
My hack for the moment is to comment out the entry in exports, then edit it after mounting any of those disks.
In this case you can simply export it manually.
I never tried that. What command? "man export" is for another thing.
exportfs man exportfs -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-01-26 13:45, Patrick Shanahan wrote:
* Carlos E. R. <> [01-26-17 07:43]:
On 2017-01-26 13:33, Andrei Borzenkov wrote:
In this case you can simply export it manually.
I never tried that. What command? "man export" is for another thing.
exportfs man exportfs
Ah, thanks. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2017-01-07 05:02, Carlos E. R. wrote:
Hi,
When I try restart syslog, I get this prompt instead.
Telcontar:~ # systemctl restart rsyslog.service Please enter passphrase for disk ST2000DM001-1CH1 (cr_other) on /data/other! Telcontar:~ #
Still hapening today :-( -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2017-01-07 at 05:02 +0100, Carlos E. R. wrote:
Hi,
When I try restart syslog, I get this prompt instead.
Telcontar:~ # systemctl restart rsyslog.service Please enter passphrase for disk ST2000DM001-1CH1 (cr_other) on /data/other! Telcontar:~ #
This has not happened again, but what is happening now is that on boot the system asks for the password for that mount. - ----- UNIT LOAD ACTIVE SUB DESCRIPTION ? apache2.service loaded failed failed The Apache Webserver ? systemd-cryptsetup@cr_other.service loaded failed failed Cryptography Setup for cr_other LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. Telcontar:~ # grep cr_other /etc/crypttab cr_other /dev/disk/by-uuid/334b5f7a-cd23-4d0a-8899-a517e5c371a5 none noauto Telcontar:~ # grep cr_other /etc/fstab /dev/mapper/cr_other /data/other xfs noauto,nofail,lazytime 1 5 Telcontar:~ # It is noauto in both /etc/crypttab and /etc/fstab, so I don't see any reason to try to mount it automatically. It also tries to mount this other one: cr_Aux_01 /dev/disk/by-uuid/fd7d909c-1e8a-40a7-b73f-29b539725c13 none noauto /dev/mapper/cr_Aux_01 /data/aux_01 xfs noauto,nofail,lazytime 1 6 A theory I have is that it is trying to fsck it, not mount it. <3.4> 2017-01-17 15:06:35 Telcontar systemd 1 - - dev-mapper-cr_other.device: Job dev-mapper-cr_other.device/start timed out. <3.3> 2017-01-17 15:06:35 Telcontar systemd 1 - - Timed out waiting for device dev-mapper-cr_other.device. <3.4> 2017-01-17 15:06:35 Telcontar systemd 1 - - Dependency failed for /data/other. <3.4> 2017-01-17 15:06:35 Telcontar systemd 1 - - Dependency failed for NFS server and services. <3.5> 2017-01-17 15:06:35 Telcontar systemd 1 - - nfs-server.service: Job nfs-server.service/start failed with result 'dependency'. <3.5> 2017-01-17 15:06:35 Telcontar systemd 1 - - data-other.mount: Job data-other.mount/start failed with result 'dependency'. <3.4> 2017-01-17 15:06:35 Telcontar systemd 1 - - Dependency failed for Cryptography Setup for cr_other. <3.5> 2017-01-17 15:06:35 Telcontar systemd 1 - - systemd-cryptsetup@cr_other.service: Job systemd-cryptsetup@cr_other.service/start failed with result 'dependency'. <3.4> 2017-01-17 15:06:35 Telcontar systemd 1 - - Dependency failed for File System Check on /dev/mapper/cr_other. <3.5> 2017-01-17 15:06:35 Telcontar systemd 1 - - systemd-fsck@dev-mapper-cr_other.service: Job systemd-fsck@dev-mapper-cr_other.service/start failed with result 'dependency'. <3.5> 2017-01-17 15:06:35 Telcontar systemd 1 - - dev-mapper-cr_other.device: Job dev-mapper-cr_other.device/start failed with result 'timeout'. - -- Cheers, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlh+J/wACgkQtTMYHG2NR9VKRACeNrnwdCjxr92Cwiv+2UG1pPwH ytwAoI+bTIlyEEuJnBpiGLUD9UQPip75 =u8O8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
17.01.2017 17:19, Carlos E. R. пишет:
On Saturday, 2017-01-07 at 05:02 +0100, Carlos E. R. wrote:
Hi,
When I try restart syslog, I get this prompt instead.
Telcontar:~ # systemctl restart rsyslog.service Please enter passphrase for disk ST2000DM001-1CH1 (cr_other) on /data/other! Telcontar:~ #
This has not happened again, but what is happening now is that on boot the system asks for the password for that mount.
-----
UNIT LOAD ACTIVE SUB DESCRIPTION ? apache2.service loaded failed failed The Apache Webserver ? systemd-cryptsetup@cr_other.service loaded failed failed Cryptography Setup for cr_other
LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type.
Telcontar:~ # grep cr_other /etc/crypttab cr_other /dev/disk/by-uuid/334b5f7a-cd23-4d0a-8899-a517e5c371a5 none noauto Telcontar:~ # grep cr_other /etc/fstab /dev/mapper/cr_other /data/other xfs noauto,nofail,lazytime 1 5 Telcontar:~ #
It is noauto in both /etc/crypttab and /etc/fstab, so I don't see any reason to try to mount it automatically.
It also tries to mount this other one:
cr_Aux_01 /dev/disk/by-uuid/fd7d909c-1e8a-40a7-b73f-29b539725c13 none noauto
/dev/mapper/cr_Aux_01 /data/aux_01 xfs noauto,nofail,lazytime 1 6
A theory I have is that it is trying to fsck it, not mount it.
<3.4> 2017-01-17 15:06:35 Telcontar systemd 1 - - dev-mapper-cr_other.device: Job dev-mapper-cr_other.device/start timed out. <3.3> 2017-01-17 15:06:35 Telcontar systemd 1 - - Timed out waiting for device dev-mapper-cr_other.device. <3.4> 2017-01-17 15:06:35 Telcontar systemd 1 - - Dependency failed for /data/other. <3.4> 2017-01-17 15:06:35 Telcontar systemd 1 - - Dependency failed for NFS server and services.
nfs-server comes with systemd generator that automatically adds RequiresMountsFor for each exported filesystem. So start of NFS server triggers mounting of these filesystems. Look at systemctl show -p RequiredBy -p WantedBy data-other.mount
On 2017-01-17 18:07, Andrei Borzenkov wrote:
17.01.2017 17:19, Carlos E. R. пишет:
On Saturday, 2017-01-07 at 05:02 +0100, Carlos E. R. wrote:
Hi,
When I try restart syslog, I get this prompt instead.
Telcontar:~ # systemctl restart rsyslog.service Please enter passphrase for disk ST2000DM001-1CH1 (cr_other) on /data/other! Telcontar:~ #
This has not happened again, but what is happening now is that on boot the system asks for the password for that mount.
-----
UNIT LOAD ACTIVE SUB DESCRIPTION ? apache2.service loaded failed failed The Apache Webserver ? systemd-cryptsetup@cr_other.service loaded failed failed Cryptography Setup for cr_other
LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type.
Telcontar:~ # grep cr_other /etc/crypttab cr_other /dev/disk/by-uuid/334b5f7a-cd23-4d0a-8899-a517e5c371a5 none noauto Telcontar:~ # grep cr_other /etc/fstab /dev/mapper/cr_other /data/other xfs noauto,nofail,lazytime 1 5 Telcontar:~ #
It is noauto in both /etc/crypttab and /etc/fstab, so I don't see any reason to try to mount it automatically.
It also tries to mount this other one:
cr_Aux_01 /dev/disk/by-uuid/fd7d909c-1e8a-40a7-b73f-29b539725c13 none noauto
/dev/mapper/cr_Aux_01 /data/aux_01 xfs noauto,nofail,lazytime 1 6
A theory I have is that it is trying to fsck it, not mount it.
<3.4> 2017-01-17 15:06:35 Telcontar systemd 1 - - dev-mapper-cr_other.device: Job dev-mapper-cr_other.device/start timed out. <3.3> 2017-01-17 15:06:35 Telcontar systemd 1 - - Timed out waiting for device dev-mapper-cr_other.device. <3.4> 2017-01-17 15:06:35 Telcontar systemd 1 - - Dependency failed for /data/other. <3.4> 2017-01-17 15:06:35 Telcontar systemd 1 - - Dependency failed for NFS server and services.
nfs-server comes with systemd generator that automatically adds RequiresMountsFor for each exported filesystem. So start of NFS server triggers mounting of these filesystems.
Look at
systemctl show -p RequiredBy -p WantedBy data-other.mount
Sorry, this post slipped my attention. Good catch! Telcontar:~ # systemctl show -p RequiredBy -p WantedBy data-other.mount RequiredBy=nfs-server.service WantedBy= Telcontar:~ # And... Telcontar:~ # cat /etc/exports | egrep -v "^[[:space:]]*$|^#" ... /data/other/ 192.168.1.0/24(fsid=1236,ro,root_squash,nohide,no_subtree_check) /data/aux_01/ 192.168.1.129(fsid=1250,rw,no_root_squash,nohide,no_subtree_check) That's the reason. I sometimes export those directories. This configuration worked fine on 13.1, but now systemd is too clever and wants to mount them before starting nfs server. And this will be the reason my nfs server fails to start, too. Sigh. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
David Haller -
John Andersen -
Patrick Shanahan