Re: Mounting internal disk spins up connected external USB disks
On 11/14/18 5:34 PM, Wolfgang Pfeiffer wrote: I'm running awesome on tty2, so gnome-shell on tty1 is still hanging around for whatever reason .. gdm is actually a special session of gnome-shell. gdm doesn't go away when you login. Try running "sudo inotifywait -m /dev" before you do the mount and see if anything shows up. I think that will tell you if it's the kernel or some process. Another thing to try is doing it from a console or ssh when you aren't logged in to the graphical session. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Mounting internal disk spins up connected external USB disks
On 11/14/18 2:38 PM, Wolfgang Pfeiffer wrote: Mounting an internally installed disk on a laptop spins up all disks connected to this machine via USB. And I try to prevent these externally connected disks to spin up. Are the externally connected disks mounted? /dev/sda: Device of type 'scsi' [SCSI] detected /dev/sda [SAT]: Device open changed type from 'scsi' to 'sat' /dev/sda [SAT]: Device of type 'sat' [ATA] opened (On a side note: I'm astonished that a smartctl simple info flag is changing some device type like shown above) Not really strange. /dev/sd* used to refer to SCSI disks, so it starts out assuming the drive is SCSI. After checking it, it determines that it's actually ATA and continues accordingly. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Thank you - F27 to F29 upgrade
I just wanted to say thank you to the developers of the upgrade. I upgraded two machines to F29 from F27 with only one small issue related to a 32bit library used by Wine. I liked the boot screen showing which packages were being installed and the increasing icon. Robin ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: HTTPD shutting down every night
So httpd survived Tuesday without crashing but crashed again yesterday and today. In /var/log/messages I can see: Nov 14 03:26:57 novak systemd[1]: Reloading The Apache HTTP Server. Nov 14 03:26:57 novak systemd[739346]: httpd.service: Failed to set up mount namespacing: No such file or directory Nov 14 03:26:57 novak systemd[739346]: httpd.service: Failed at step NAMESPACE spawning /usr/sbin/httpd: No such file or directory Nov 14 03:26:57 novak systemd[1]: httpd.service: Control process exited, code=exited status=226 And then a little later Nov 14 03:26:58 novak systemd[1]: httpd.service: Killing process 230630 (nss_pcache) with signal SIGKILL. Nov 14 03:26:58 novak systemd[1]: httpd.service: Failed with result 'exit-code'. Nov 14 03:26:58 novak systemd[1]: Reload failed for The Apache HTTP Server. Nov 14 03:26:58 novak audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=httpd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Nov 14 03:26:58 novak logrotate[739362]: ALERT exited abnormally with [1] Googling the NAMESPACE error I find a post about /tmp or /var/tmp being symbolic links. Neither are. Yesterday I reinstalled httpd from scratch, last night it crashed again in the same way. Does anyone know what user logrotate runs as? I’ve tried /bin/systemctl reload httpd.service as root and it reloads as expected and am wondering if there’s something else weird going on here? Regards, Scott > On 12. Nov 2018, at 16:32, Scott van Looy via users > wrote: > > Thanks for this. > > Certwatch is uninstalled now, it just tells me if any of my certs have > expired and as I don’t have any on that box any more it’s kinda pointless :) > > I’ve removed the stuff to hide the output from the apache restart in > logrotate so I’m going to let it run tonight and see if anything exciting > gets logged > > Regards, > > Scott > >> On 12. Nov 2018, at 16:08, Andy Blanchard wrote: >> >> Of that bunch, autodld (downloading RPMs) and rkhunter (scanning the >> filesystem, taking checksums, and looking for changes) are both >> passive, certwatch probably shouldn't be updating certificates every >> 24 hours (but could do, so worth checking!), and logwatch just parses >> the existing logfiles - it shouldn't touch the daemons. That leaves >> logrotate as the prime suspect, IMHO, as that definitely HUPs/restarts >> daemons after it rotates logfiles. However, it also tracks when it >> was last run and won't cycle a logfile and HUP a daemon if it doesn't >> need to - since it's already cycled the logs at 03:54, it won't do so >> again when you're trying to run it manually unless you tweak the file >> "/var/lib/logrotate.status" first. >> >> Note also that httpd exited within the window for logrotate, which >> also seems to point the finger at logrotate, so I'd definitely make >> sure that was in tonight's list of disabled scripts, and it might be >> worth double checking what update cycle certwatch is using too. >> >> Andy >> ___ >> users mailing list -- users@lists.fedoraproject.org >> To unsubscribe send an email to users-le...@lists.fedoraproject.org >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Mounting internal disk spins up connected external USB disks
On Wed, Nov 14, 2018 at 06:48:17PM -0500, Tom Horsley wrote: On Wed, 14 Nov 2018 23:38:39 +0100 Wolfgang Pfeiffer wrote: Anyone an idea about where to start investigating this issue? Where could such behaviour possibly be set up? If you are using gnome it just loves to seek out disks and access them any time any kind of a file dialog opens. Window Manager is Awesome WM, Display manager is GDM. But there are some pieces of Gnome still running here as I still use Gnome apps occasionally on awesome ... % ps ax | grep -i gnom\[e\] 1422 tty1 Ssl+ 0:00 /usr/libexec/gdm-wayland-session gnome-session --autostart /usr/share/gdm/greeter/autostart 1507 tty1 Sl+0:00 /usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart 1522 tty1 Sl+0:18 /usr/bin/gnome-shell 1769 ?Sl 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session 6777 ?Sl 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login 7049 ?Sl 0:20 /usr/libexec/at-spi2-registryd --use-gnome-session 7127 ?Ssl8:24 /usr/libexec/gnome-terminal-server 7391 ?Sl 0:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets I'm running awesome on tty2, so gnome-shell on tty1 is still hanging around for whatever reason .. This once worked, but may not any longer: https://tomhorsley.com/game/case-of-disks.html Also systemd seems to have an affinity for touching disks as well. The external disks don't get mounted, they just spin up the moment I start acting, for example when manually mounting an internal HDD. The behavior seems new: I run Fedora since ~2 yrs, and I noticed the USB disks spinning up only a few months ago - no changes since then that I'd remember of. And I don't think it's some hardware specific thing, as different disks show the same unwanted behavior. One of those external disks even is spinning up after issuing this command: - # smartctl -d sat -P show -n sleep,0 /dev/sdd smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.18.17-200.fc28.x86_64] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org Device is in SLEEP mode, exit(0) The 'n' flag above should make sure the disk isn't spun up when querying it, but nonetheless: the disk is rightly identified as being in sleep mode, but spins up anyways a second after issuing the command. All I can do is manually spinning it down again: sdparm --readonly -C stop /dev/sdd I'm still hoping there is a setting somewhere in /etc (or wherever) that controls this situation ... I have a USB disk for backups that is normally not mounted, is listed in /etc/fstab with "noauto", yet recently I've noticed every time I reboot, I have to wait for some systemd message about syncing headers on disk [sdf] (which takes a while because the disk is very slow and has to spin up first). I don't see any journalctl messages about the disks spun up, but I might find a setting for journalctl to log the behavior. Not sure when it started happening, but it certainly didn't always happen because it is irritating enough to notice. See? - so it seems it's not just me seeing this. So either there's some buggy piece of software somewhere, or some setting was changed at some point Wolfgang ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Mounting internal disk spins up connected external USB disks
On Wed, 14 Nov 2018 23:38:39 +0100 Wolfgang Pfeiffer wrote: > Anyone an idea about where to start investigating this issue? Where > could such behaviour possibly be set up? If you are using gnome it just loves to seek out disks and access them any time any kind of a file dialog opens. This once worked, but may not any longer: https://tomhorsley.com/game/case-of-disks.html Also systemd seems to have an affinity for touching disks as well. I have a USB disk for backups that is normally not mounted, is listed in /etc/fstab with "noauto", yet recently I've noticed every time I reboot, I have to wait for some systemd message about syncing headers on disk [sdf] (which takes a while because the disk is very slow and has to spin up first). Not sure when it started happening, but it certainly didn't always happen because it is irritating enough to notice. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Mounting internal disk spins up connected external USB disks
Mounting an internally installed disk on a laptop spins up all
disks connected to this machine via USB. And I try to prevent these
externally connected disks to spin up.
The behaviour, IIRC, started a few months ago on the previous F27 and
continues now on F28. Before that I don't remember this behaviour to
have happened.
I thought it was some smartd issue, and stopped this service
("/usr/bin/systemctl stop smartd.service") - to no avail: mounting the
internal disk still spins up the external ones.
The internal disk is identified by "smartctl -d test /dev/sda" like
so:
[ ... ]
/dev/sda: Device of type 'scsi' [SCSI] detected
/dev/sda [SAT]: Device open changed type from 'scsi' to 'sat'
/dev/sda [SAT]: Device of type 'sat' [ATA] opened
(On a side note: I'm astonished that a smartctl simple info flag is
changing some device type like shown above)
External disks are identified by a smartctl test like so:
One:
"[USB Sunplus]: Device of type 'usbsunplus' [ATA] detected"
the other one:
"[SAT]: Device of type 'sat' [ATA] detected"
Anyone an idea about where to start investigating this issue? Where
could such behaviour possibly be set up?
Thanks in anticipation.
Wolfgang
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
