[Bug 1392647] [NEW] smbstatus reports dead connection as active
Public bug reported: I have a home server running ubuntu 14.04.1 LTS. It was setup originally with ubuntu 12.04 LTS and running satisfactorily for more than 2 years The server checks every 10 minutes and goes to sleep if no active clients are detected. My main PC is a w7 box connecting to some samba shares on the server. In the past 3 weeks it happened 3 times that the server reported an active samba connection although the client had long been shutdown. At the first occurrence I set the deadtime parameter to 10 but this did not solve the problem. The deadtime parameter was not there at all for the past 2 years and the problem only showed up lately so I think the cause of problem is somewhere else. This is the output of smbstatus -v taken about 2 hours after the client has been powered off. It should not show the 4366 PID lines. Samba version 4.1.6-Ubuntu PID Username Group Machine --- 4366 fatherfather192.168.101.69 (ipv4:192.168.101.69:2132) Opened /var/run/samba/connections.tdb Service pid machine Connected at --- HomeServer 4366 192.168.101.69 Thu Nov 13 19:03:04 2014 Locked files: Pid UidDenyMode Access R/WOplock SharePath Name Time -- 4366 1000 DENY_NONE 0x100081RDONLY NONE /Data.Home . Thu Nov 13 19:03:04 2014 apt-cache policy samba reports samba: Installed: 2:4.1.6+dfsg-1ubuntu2.14.04.3 Candidate: 2:4.1.6+dfsg-1ubuntu2.14.04.3 Version table: *** 2:4.1.6+dfsg-1ubuntu2.14.04.3 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 2:4.1.6+dfsg-1ubuntu2 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages My list of installed packages is attached. ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Attachment added: "list of installed software packages" https://bugs.launchpad.net/bugs/1392647/+attachment/4260412/+files/xyz -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1392647 Title: smbstatus reports dead connection as active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1392647/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1281447] Re: false positive in logwatch report
To my understanding it is normal behaviour that during boot the root filesystem is first mounted ro and after it has passed some checks it gets remounted. Logwatch seems to just to check the fstab line in the log file, see the error option and report it as a false positive. It is a false positive because the line says "in case of an error, remount as ro" but the file system in fact gets remounted as rw after it was initially mounted as ro. So the line from fstab appears in the dmesg log and logwatch unfortunately just seems to trigger on the word error. The same thing happens with the entry "ERST: Error Record Serializa" which gets me a logwatch error after every boot. I hope that future versions of logwatch will have an option to filter those false positives which are a real nag to me. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1281447 Title: false positive in logwatch report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1281447/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1281447] [NEW] false positive in logwatch report
Public bug reported: I always get the following false positives reported from dmesg. ERST: Error Record Serializa ...: 2 Time(s) EXT4-fs (sdc1): re-mounted. Opts: errors=remount-ro ...: 2 Time(s) Both messages are obviously not errors. It seems that logwatch is just looking for words like "error" and there is no exclusion filter for false positives. ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1281447 Title: false positive in logwatch report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1281447/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1005440] Re: "Could not load host key: /etc/ssh/ssh_host_ecdsa_key" when connecting
I setup a vServer with ubuntu 12.04.02 LTS last week using the image that my provider has supplied and I get the same error reported from logwatch. "error: Could not load host key: /etc/ssh/ssh_host_ecdsa_key" Looking at the /etc/ssh I only see: ssh_config sshd_config ssh_host_dsa_key ssh_host_dsa_key.pub ssh_host_key ssh_host_key.pub ssh_host_rsa_key ssh_host_rsa_key.pub Strange enough I did not notice any problems not having the ecdsa key except the message from logwatch. So what is it needed for anyway? Nevertheless I created the ecdsa key using ssh-keygen -f /etc/ssh/ssh_host_ecdsa_key -N '' -t ecdsa to get rid of the message. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1005440 Title: "Could not load host key: /etc/ssh/ssh_host_ecdsa_key" when connecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1005440/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1091114] [NEW] fuse mount cause problem to find -xdev
Public bug reported: find . -xdev reports "Permission denied" on fuse mounts instead of skipping the mount point. I found various bug reports on fuse mounts and it seems that fuse mounts are still not properly handled with 12.04.1 LTS. Programs like x2go create a fuse mount in /tmp ! e.g. mount | grep fuse gvfs-fuse-daemon on /var/lib/lightdm/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=lightdm) testuser@127.0.0.1:/media on /tmp/.x2go-testuser/media/disk/_media type fuse.sshfs (rw,nosuid,nodev,max_read=65536,user=testuser) So when a root cron job does something like find /tmp -xdev (e.g. to cleanup old stuff) find does not skip the mount point but reports a permission denied error. This is not a clean behaviour. Either find should correctly skip this mount point or root should be able to scan everything on a machine. To my opinion root is root is root, so there should be no restrictions on following fuse mounts. As root can su to the user or even change the users password and become the user, I do not see any reason why root is restricted to follow fuse mounts right away. ** Affects: checksecurity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to checksecurity in Ubuntu. https://bugs.launchpad.net/bugs/1091114 Title: fuse mount cause problem to find -xdev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checksecurity/+bug/1091114/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
