search for: 22min

...- ] urandom [ - ] uuidd [ - ] winbind [ - ] x11-common We are seeing issues with winbind * winbind.service - Samba Winbind Daemon Loaded: loaded (/lib/systemd/system/winbind.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-05-06 02:14:54 UTC; 22min ago Docs: man:winbindd(8) man:samba(7) man:smb.conf(5) Process: 145 ExecStart=/usr/sbin/winbindd --foreground --no-process-group $WINBINDOPTIONS (code=exited, status=1/FAILURE) Main PID: 145 (code=exited, status=1/FAILURE) May 06 02:14:54 linserver01 systemd[1]: Starti...

...I have seen it one other time (don't remember the details). systemctl status puppetmaster ? puppetmaster.service - Puppet master Loaded: loaded (/lib/systemd/system/puppetmaster.service; enabled; vendor preset: enabled) Active: failed (Result: resources) since Tue 2017-08-29 11:24:36 CDT; 22min ago Process: 897 ExecStart=/usr/bin/puppet master (code=exited, status=0/SUCCESS) Aug 29 11:22:39 puppetmaster02 systemd[1]: Starting Puppet master... Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Reopening log files Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Starting Puppet mas...

...ng Samba 4.6.3 as DC and Samba 4.1.17 as File Server. When I restart Samba Service, this message appears: root at dc1:/root# /etc/init.d/samba4 status ● samba4.service - LSB: start Samba4 daemons Loaded: loaded (/etc/init.d/samba4) Active: active (running) since Ter 2017-06-13 00:27:08 -03; 22min ago Process: 587 ExecStop=/etc/init.d/samba4 stop (code=exited, status=0/SUCCESS) Process: 596 ExecStart=/etc/init.d/samba4 start (code=exited, status=0/SUCCESS) CGroup: /system.slice/samba4.service ├─601 /usr/local/samba/sbin/samba -D ├─626 /usr/local/samba/sbin/samba...

...you are using it as a fileserver. > We are seeing issues with winbind > > * winbind.service - Samba Winbind Daemon > Loaded: loaded (/lib/systemd/system/winbind.service; enabled; > vendor preset: enabled) Active: failed (Result: exit-code) since Mon > 2019-05-06 02:14:54 UTC; 22min ago Docs: man:winbindd(8) > man:samba(7) > man:smb.conf(5) > Process: 145 ExecStart=/usr/sbin/winbindd --foreground > --no-process-group $WINBINDOPTIONS (code=exited, status=1/FAILURE) > Main PID: 145 (code=exited, status=1/FAILURE) > > May 06 02:14:54...

...but I have seen it one other time (don't remember the details). systemctl status puppetmaster ? puppetmaster.service - Puppet master Loaded: loaded (/lib/systemd/system/puppetmaster.service; enabled; vendor preset: enabled) Active: failed (Result: resources) since Tue 2017-08-29 11:24:36 CDT; 22min ago Process: 897 ExecStart=/usr/bin/puppet master (code=exited, status=0/SUCCESS) Aug 29 11:22:39 puppetmaster02 systemd[1]: Starting Puppet master... Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Reopening log files Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Starting Puppet master...

2. Recommendations? My use case is pretty typical. I have one Linux machine I want to protect, automated shutown is desirable, blackouts longer than a hour are very rare at my location (the last one I can remember was in 1993), brownouts are very rare and mild, but summer thunderstorms are common and can be severe. I'm a good match for your typical consmer-grade UPS. 2a. In 2009, what do

...but I have seen it one other time (don't remember the details). systemctl status puppetmaster ? puppetmaster.service - Puppet master Loaded: loaded (/lib/systemd/system/puppetmaster.service; enabled; vendor preset: enabled) Active: failed (Result: resources) since Tue 2017-08-29 11:24:36 CDT; 22min ago Process: 897 ExecStart=/usr/bin/puppet master (code=exited, status=0/SUCCESS) Aug 29 11:22:39 puppetmaster02 systemd[1]: Starting Puppet master... Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Reopening log files Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Starting Puppet master...

...to serve connections But even after restaring smbd, it doesn't find winbindd: server2 /root# rcsmb status * smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2019-11-28 16:47:35 CET; 22min ago Main PID: 26379 (smbd) Status: "smbd: ready to serve connections..." Tasks: 4 (limit: 4915) CGroup: /system.slice/smb.service |-26379 /usr/sbin/smbd --foreground --no-process-group |-26381 /usr/sbin/smbd --foreground --no-process-group...

...ou are using it as a fileserver. > We are seeing issues with winbind > > * winbind.service - Samba Winbind Daemon > Loaded: loaded (/lib/systemd/system/winbind.service; enabled; > vendor preset: enabled) Active: failed (Result: exit-code) since Mon > 2019-05-06 02:14:54 UTC; 22min ago Docs: man:winbindd(8) > man:samba(7) > man:smb.conf(5) > Process: 145 ExecStart=/usr/sbin/winbindd --foreground > --no-process-group $WINBINDOPTIONS (code=exited, status=1/FAILURE) > Main PID: 145 (code=exited, status=1/FAILURE) > > May 06 02:14:5...

...as systemctl status smbd shows: > root at pi4b:~# systemctl status smbd > ?$B!| smbd.service - Samba SMB Daemon > Loaded: loaded (/lib/systemd/system/smbd.service; enabled; > vendor preset: enabled) > Active: failed (Result: core-dump) since Tue 2020-02-04 > 20:32:52 GMT; 22min ago > Docs: man:smbd(8) > man:samba(7) > man:smb.conf(5) > Process: 493 > ExecStartPre=/usr/share/samba/update-apparmor-samba-profile > (code=exited, status=0/SUCCESS) > Process: 495 ExecStart=/usr/sbin/smbd --foreground > --no-process-group...

Roy, Im still wondering what your problem might be/where its coming from. But we know it's interface/network related, only thing is Samba should not coredump. So i had a good look below to see where im missing what. And i dont see much to work with. I have 2 possible options where, where a problem might be. 1) samba start before network is online. A possible workaround is add in all