search for: disonnect

Hello, I am having the same problem as below. I am using 3.02a on FreeBSD. Was this solved or does anyone know how to solve it? Many Thanks, Chetana On Wed, May 26, 2004 at 09:54:18AM +0200, yves.lejeune at kodak.com wrote: > Hello, > > > > > > > Is is normal to have the initial double SMB_VFS_CONNECT and > > > SMB_VFS_DISCONNECT ? > > > Should I

...l/samba/var/locks/sysvol" (bug #9820). o Fix segmentation fault while reading incomplete session info (bug #10003). o smbd: Fix a 100% loop at shutdown time (bug #10013). Changes since 4.0.8: -------------------- o Michael Adam <obnox at samba.org> * BUG 9930: smbd: Cleanup disonnected durable handles. o Jeremy Allison <jra at samba.org> * BUG 9992: Fix Windows error 0x800700FE when copying files with xattr names containing ":". * BUG 10064: Linux kernel oplock breaks can miss signals. o Andrew Bartlett <abartlet at samba.org> * B...

...l/samba/var/locks/sysvol" (bug #9820). o Fix segmentation fault while reading incomplete session info (bug #10003). o smbd: Fix a 100% loop at shutdown time (bug #10013). Changes since 4.0.8: -------------------- o Michael Adam <obnox at samba.org> * BUG 9930: smbd: Cleanup disonnected durable handles. o Jeremy Allison <jra at samba.org> * BUG 9992: Fix Windows error 0x800700FE when copying files with xattr names containing ":". * BUG 10064: Linux kernel oplock breaks can miss signals. o Andrew Bartlett <abartlet at samba.org> * B...

Hi, I have virt-manager 0.9 connecting to a libvirtd 0.9.3 on Debian unstable. Hypervisor being used is KVM. In a VM, I can select the "IDE CDROM 1" and click on "disonnect" which makes the virtual disk disappear from the virtual drive and the former disconnect button now reads "connect". Hence, when I click there, nothing happens. Currently, the only way I am aware to get a new CD in the virtual drive is to delete it and to add a new virtual CD drive....

...> >So one question that remains is the missing lines from previous lifetime in >the short excerpt of upsd: why did it restart at that time? :) I also have Eaton UPS, just different model. It sometimes disconnects and nut has to connect again. I guess this is what happened. I assume the disonnect message is not visible in "Systemctl status" message because it does not belong to the current process but previous one. Looking for syslog (/var/log/messages) or journal messages (journalctl) could show that. I guess nothing bad happened there. >On Fri, Jan 19, 2024 at 6:13?AM Stef...

...emains is the missing lines from previous lifetime > in > >the short excerpt of upsd: why did it restart at that time? :) > > I also have Eaton UPS, just different model. It sometimes disconnects and > nut has to connect again. I guess this is what happened. > > I assume the disonnect message is not visible in "Systemctl status" > message > because it does not belong to the current process but previous one. > Looking for syslog (/var/log/messages) or journal messages (journalctl) > could > show that. I guess nothing bad happened there. > > >On F...

...ng lines from previous lifetime in >> >the short excerpt of upsd: why did it restart at that time? :) >> >> I also have Eaton UPS, just different model. It sometimes disconnects and >> nut has to connect again. I guess this is what happened. >> >> I assume the disonnect message is not visible in "Systemctl status" message >> because it does not belong to the current process but previous one. >> Looking for syslog (/var/log/messages) or journal messages (journalctl) could >> show that. I guess nothing bad happened there. >> >&gt...

...ifetime in >>> >the short excerpt of upsd: why did it restart at that time? :) >>> >>> I also have Eaton UPS, just different model. It sometimes disconnects and >>> nut has to connect again. I guess this is what happened. >>> >>> I assume the disonnect message is not visible in "Systemctl status" message >>> because it does not belong to the current process but previous one. >>> Looking for syslog (/var/log/messages) or journal messages (journalctl) could >>> show that. I guess nothing bad happened there. >...

...gt;the short excerpt of upsd: why did it restart at that time? :) > >>> > >>> I also have Eaton UPS, just different model. It sometimes disconnects and > >>> nut has to connect again. I guess this is what happened. > >>> > >>> I assume the disonnect message is not visible in "Systemctl status" message > >>> because it does not belong to the current process but previous one. > >>> Looking for syslog (/var/log/messages) or journal messages (journalctl) could > >>> show that. I guess nothing bad happe...

Well, from your logs it seems that at 05:17:03 your nut-server (upsd) restarted, so an upsmon reconnection attempt at 05:17:09 had an issue with that (config not all applied? strange a bit) but since 05:17:14 it is okay. Maybe a few too many banners shown from upsmon, while its same uptime seems to continue. Maybe someone should check on that, seems like a good and easy newcomer issue to learn