Re: [CentOS] rare but repeating system crash in C7
Yeah, and the instructions for setting RAID-1 or RAID-0 have the switch positions exactly reversed. Strahil: I'm using autofs to automount the unit. but just turned that off and enabled the xsystemd.automount in fstab, we'll see how that works. Fred On Sat, Jan 2, 2021 at 4:11 PM Warren Young wrote: > On Jan 2, 2021, at 11:17 AM, Fred wrote: > > > > I assume that the yottamaster device runs Linux, just like 99% of other > > such devices. > > 99% of NAS boxes, maybe, but not dumb RAID boxes like the one I believe > you’re referring to. > > (And I doubt even that, with the likes of FreeNAS extending down from the > enterprise space where consumer volume can affect that sort of thing.) > > I have more than speculation to back that guess: the available firmware > images are far too small to contain a Linux OS image, their manuals don’t > talk about Linux or GPL that I can see, and there’s no place to download > their Linux source code per the GPL. > > While doing this exploration, I’ve run into multiple problems with their > web site, which strengthens my suspicion that this box is your culprit. If > they’re this slipshod with their marketing material, what does that say > about their engineering department? > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rare but repeating system crash in C7
On Jan 2, 2021, at 11:17 AM, Fred wrote: > > I assume that the yottamaster device runs Linux, just like 99% of other > such devices. 99% of NAS boxes, maybe, but not dumb RAID boxes like the one I believe you’re referring to. (And I doubt even that, with the likes of FreeNAS extending down from the enterprise space where consumer volume can affect that sort of thing.) I have more than speculation to back that guess: the available firmware images are far too small to contain a Linux OS image, their manuals don’t talk about Linux or GPL that I can see, and there’s no place to download their Linux source code per the GPL. While doing this exploration, I’ve run into multiple problems with their web site, which strengthens my suspicion that this box is your culprit. If they’re this slipshod with their marketing material, what does that say about their engineering department? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rare but repeating system crash in C7
> Just add "x-systemd.automount,x-systemd.idle-timeout=10min" in the > fstab mount options , or create an ".mount" + ".automount" entries > for > it (autofs is also an option) and test. If you picked the systemd automounter as an option, you will have to run: systemctl restart local-fs.target Best Regards, Strahil Nikolov ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rare but repeating system crash in C7
> I assume that the yottamaster device runs Linux, just like 99% of > other > such devices. as to whether it uses linux software raid or some cheap > (megaraid???) chipset, I don't know, nor know how to tell. but I'll > check > that URL you sent and see what happens. Just add "x-systemd.automount,x-systemd.idle-timeout=10min" in the fstab mount options , or create an ".mount" + ".automount" entries for it (autofs is also an option) and test. The "x-systemd.automount" option will tell systemd to create a ".automount" unit which will monitor the mount point and automatically mount your drive, while the idle-timeout will tell systemd to automatically umount the share when not in use (ls, df, du and others count as usage and reset the counter). Also , if you use 7.6 - there is a bug in sysstat that forces autofs and systemd's automounter to mount the share. Best Regards, Strahil Nikolov ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rare but repeating system crash in C7
Warren, thanks for the additional info. I assume that the yottamaster device runs Linux, just like 99% of other such devices. as to whether it uses linux software raid or some cheap (megaraid???) chipset, I don't know, nor know how to tell. but I'll check that URL you sent and see what happens. Thanks again! Fred On Sat, Jan 2, 2021 at 12:28 PM Warren Young wrote: > On Jan 2, 2021, at 9:55 AM, Fred wrote: > > > > Plantronics USB headset/microphone? > > Yottamaster RAID-1 storage (USB3)? > > Behringer USB audio interface? > > Logitech wireless mouse? > > Leopold USB keyboard? > > HID devices won’t go to sleep when the computer does, else they couldn’t > wake it back up. (Keyboard & mouse, mainly.) > > The two audio interfaces may or may not sleep. Try checking their > indicator LEDs when the computer goes to sleep: I’d expect them to visibly > show that they’ve gone to sleep if they do. If they do, then on wake, they > *could* do this sort of thing. > > I’d go after the RAID enclosure first, particularly if it’s hardware RAID, > since that means it’s “clever,” thus suspect. Check that you’ve got the > current firmware: > > https://www.yottamaster.com/?route=common/driver > > If it’s one of their JBOD models, requiring that you do some sort of > software RAID, I’d expect a much different report in the kernel log if the > corresponding software RAID component had a bug, which would mean it’s got > some fundamental USB compatibility problem if that’s the device causing the > problem. Again, check for firmware updates. > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rare but repeating system crash in C7
On Jan 2, 2021, at 9:55 AM, Fred wrote: > > Plantronics USB headset/microphone? > Yottamaster RAID-1 storage (USB3)? > Behringer USB audio interface? > Logitech wireless mouse? > Leopold USB keyboard? HID devices won’t go to sleep when the computer does, else they couldn’t wake it back up. (Keyboard & mouse, mainly.) The two audio interfaces may or may not sleep. Try checking their indicator LEDs when the computer goes to sleep: I’d expect them to visibly show that they’ve gone to sleep if they do. If they do, then on wake, they *could* do this sort of thing. I’d go after the RAID enclosure first, particularly if it’s hardware RAID, since that means it’s “clever,” thus suspect. Check that you’ve got the current firmware: https://www.yottamaster.com/?route=common/driver If it’s one of their JBOD models, requiring that you do some sort of software RAID, I’d expect a much different report in the kernel log if the corresponding software RAID component had a bug, which would mean it’s got some fundamental USB compatibility problem if that’s the device causing the problem. Again, check for firmware updates. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rare but repeating system crash in C7
Warren, thanks for the reply! Plantronics USB headset/microphone? Yottamaster RAID-1 storage (USB3)? Behringer USB audio interface? Logitech wireless mouse? Leopold USB keyboard? Does any one of them sound more likely than the others? Of all those, the yottamaster device is the most recent. Unfortunately I haven't kept notes on when it occurs, so it's possible it was occurring before I got that device. :( If it is that device (used primarily for nightly backups) might it help if I unmount it after each use? Thanks in advance! Fred On Sat, Jan 2, 2021 at 11:13 AM Warren Young wrote: > On Jan 2, 2021, at 7:44 AM, Fred wrote: > > > > I'm further guessing that "xhci_hcd" has something to do with USB > > Yup: > https://en.wikipedia.org/wiki/Extensible_Host_Controller_Interface#Virtualization_support > > > If so I don't know what it would be... > > My guess: you have USB-attached storage that’s waking up when you wiggle > the mouse, and it’s crashing the bus, kicking the kernel driver over, so > the system reboots to protect itself. > > If not storage, then something else sufficiently complicated, which wakes > up when you wake the system. > > I’d exclude things like optical drives, unless they have disks in them at > the time this happens. > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rare but repeating system crash in C7
On Jan 2, 2021, at 7:44 AM, Fred wrote: > > I'm further guessing that "xhci_hcd" has something to do with USB Yup: https://en.wikipedia.org/wiki/Extensible_Host_Controller_Interface#Virtualization_support > If so I don't know what it would be... My guess: you have USB-attached storage that’s waking up when you wiggle the mouse, and it’s crashing the bus, kicking the kernel driver over, so the system reboots to protect itself. If not storage, then something else sufficiently complicated, which wakes up when you wake the system. I’d exclude things like optical drives, unless they have disks in them at the time this happens. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] rare but repeating system crash in C7
Hi all, I'm hoping someone can help me figure this out. every now and then (less than monthly, maybe every 2-4 months, or so, I'll walk up to my C7 box (my home PC) in the morning, wiggle the mouse to wake up the screen, and after a second or so, instead of a live screen, the keyboard shift-lock and scroll-lock keys light up. if I wait a few (tens of) second(s) I find it is rebooting, as the BIOS splash screen appears. it boots normally and comes up with everything apparently working fine. Note that I tend to leave myself logged in 24/7/365 since there's nobody here except my wife and myself, and she has her own Linux box. as it happened again this morning, I grabbed some lines from /var/log/messages that show the last few minutes before it rebooted and the first 3 or four statements as it began to reboot: Jan 2 08:50:12 fcshome kernel: xhci_hcd :03:00.0: Looking for event-dma a9f2cb10 trb-start a9f2cb20 trb-end a9f2cb20 seg-start a9f2c000 seg-end a9f2cff0 Jan 2 08:50:13 fcshome kernel: xhci_hcd :03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:50:13 fcshome kernel: xhci_hcd :03:00.0: Looking for event-dma 164858d0 trb-start 164858e0 trb-end 164858e0 seg-start 16485000 seg-end 16485ff0 Jan 2 08:51:12 fcshome dbus[1192]: [system] Activating service name='org.fedoraproject.Setroubleshootd' (using servicehelper) Jan 2 08:51:13 fcshome dbus[1192]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd' Jan 2 08:51:14 fcshome setroubleshoot: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock. For complete SELinux messages run: sealert -l e4620dcc-6cdc-460d-a8a4-db9ce9624646 Jan 2 08:51:14 fcshome python: SELinux is preventing /usr/sbin/smbd from read access on the sock_file cups.sock.#012#012* Plugin catchall (100. confidence) suggests **#012#012If you believe that smbd should be allowed read access on the cups.sock sock_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'lpqd' --raw | audit2allow -M my-lpqd#012# semodule -i my-lpqd.pp#012 Jan 2 08:55:11 fcshome kernel: xhci_hcd :03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:55:11 fcshome kernel: xhci_hcd :03:00.0: Looking for event-dma 16485d20 trb-start 16485d30 trb-end 16485d30 seg-start 16485000 seg-end 16485ff0 Jan 2 08:55:11 fcshome kernel: xhci_hcd :03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:55:11 fcshome kernel: xhci_hcd :03:00.0: Looking for event-dma a9f2cae0 trb-start a9f2caf0 trb-end a9f2caf0 seg-start a9f2c000 seg-end a9f2cff0 Jan 2 08:58:00 fcshome kernel: xhci_hcd :03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:58:00 fcshome kernel: xhci_hcd :03:00.0: Looking for event-dma a9f2c530 trb-start a9f2c540 trb-end a9f2c540 seg-start a9f2c000 seg-end a9f2cff0 Jan 2 08:59:51 fcshome kernel: xhci_hcd :03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:59:51 fcshome kernel: xhci_hcd :03:00.0: Looking for event-dma a9f2c340 trb-start a9f2c350 trb-end a9f2c350 seg-start a9f2c000 seg-end a9f2cff0 Jan 2 08:59:51 fcshome kernel: xhci_hcd :03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 08:59:51 fcshome kernel: xhci_hcd :03:00.0: Looking for event-dma a9f2cfb0 trb-start a9f2cfc0 trb-end a9f2cfc0 seg-start a9f2c000 seg-end a9f2cff0 Jan 2 09:00:02 fcshome systemd: Created slice User Slice of root. Jan 2 09:00:02 fcshome systemd: Started Session 7364 of user root. Jan 2 09:00:02 fcshome systemd: Removed slice User Slice of root. Jan 2 09:00:06 fcshome kernel: xhci_hcd :03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:00:06 fcshome kernel: xhci_hcd :03:00.0: Looking for event-dma a9f2cd20 trb-start a9f2cd30 trb-end a9f2cd30 seg-start a9f2c000 seg-end a9f2cff0 Jan 2 09:00:59 fcshome kernel: xhci_hcd :03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8 comp_code 13 Jan 2 09:00:59 fcshome kernel: xhci_hcd :03:00.0: Looking for event-dma 16485400 trb-start 16485410 trb-end 16485410 seg-start 16485000 seg-end 16485ff0 Jan 2 09:00:59 fcshome kernel: xhci_hcd :03:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 8
Re: [CentOS-es] Que rumbo piensa seguir este grupo de listeros?
Hola Gino: El tema es que no serán paquetes oficiales... yo en lo personal considero que eso implica peligro para la producción... El tema es que CentOS Stream se convierte prácticamente en un Fedora... Mira CentOS como lo conocemos actualmente desaparece... pero otros proyectos pueden aparecer, porque RHEL ligue existiendo y NADA te impide coger esos SRPM y pre compilarlos para ti mismo... yo en teoría pienso que el proyecto seguirá su rumbo y otras variantes aparecerán o quizá usar mi CentOS para convertirlo en un RHEL a la larga... usando el mismo método. De igual forma lo ideal sería mirar a otra dirección... CentOS Stream se convierte en algo así como un Debian SID inapropiado para un servidor de producción, aunque nadie ni nada te lo impide... Yo no pondría un SID, un Fedora o cualquier otra distro que al menos no tenga un TTL de unos 5 años como servidor. Saludos, David El mar, 29 dic 2020 a las 12:38, Gino Alania () escribió: > Estimados Todos : > > Como comentario de mi parte yo seguiré con Centos, entiendo que el Centos > que lo conocemos es el Software viejo y estable que se libera a partir de > RHEL y se compila meses después para formar Centos, seamos honestos , > cuánto de nosotros tenemos repos adicionales por que no esperamos a que RHE > libere por ejemplo PHP 7.3 o sup, ahora Centos pasa a ser Centos Stream , > es como el RHEL Beta , para muchos este es un susto , para otros es una > oportunidad, por que nos va a permitir contar con un software más actual y > tener más dinámico las red de foros ya que siendo sinceros, ya no se tenía > dinámico esto por que todo se soportaba en el viejo RedHat . > RedHat Beta o Centos como será en el mediano plazo tampoco es un Software > tan inestable , por que ha pasado por cosas como Fedora Server Alpha , > Fedora Server , y posterior y muy posterior será incluido en Centos Stream > o el nuevo Centos. > > Como reitero para mí más que un susto o preocupación es una oportunidad , > no sé cómo lo vean uds. ? > > slds > > > - > Mg Gino F. Alania Hurtado > http://lab.nitcom.com > https://www.linkedin.com/in/galania > TW: @galania > - > > > El vie, 18 dic 2020 a las 15:28, Ing. H. Anibal Talingo G. via CentOS-es (< > centos-es@centos.org>) escribió: > > > Muy buenos dias a todos. > > > > Sigo a esta lista desde hace unos 8 años (quizá mas; > > > > no tengo la certeza, ya que hace unos meses borré miles de correos > > antiguos; > > > > sin embargo conservo algunos de esta lista, con fecha de Mayo de > > 2013...je je je) > > > > > > A lo largo de este tiempo, las respuestas a mis preguntas por parte del > > grupo, me han > > ayudado mucho en la resolución de varios problemas. Gracias a todos por > > su apoyo. > > > > > > Ahora que el tema (tan sonado en Internet por cierto) de > > IBM-CentOS-RedHat está > > en boca de tantos profesionales de las IT, me pregunto: > > > > Cual es el futuro de este grupo? > > > > Me queda claro, que es muy pronto para responder, que hay varias > > alternativas (como lo > > decia EPE en su video, muy bueno por cierto) pero lo que si veo claro es > > que: > > > > CentOS, deja absolutamente de ser CentOS (como lo conociamos hasta hace > > poco) > > y dificilmente volverá a ser lo que era. > > > > > > Quedo al pendiente de todos sus atinados comentarios. > > > > > > > > ___ > > CentOS-es mailing list > > CentOS-es@centos.org > > https://lists.centos.org/mailman/listinfo/centos-es > > > ___ > CentOS-es mailing list > CentOS-es@centos.org > https://lists.centos.org/mailman/listinfo/centos-es > ___ CentOS-es mailing list CentOS-es@centos.org https://lists.centos.org/mailman/listinfo/centos-es
