[Bug 856916] New: Boot Instructions for Starting LSB: Kernel based NFS Daemon and SuSEfirewall2 Create Excessive Delays in Nominal Boot Times
https://bugzilla.novell.com/show_bug.cgi?id=856916 https://bugzilla.novell.com/show_bug.cgi?id=856916#c0 Summary: Boot Instructions for Starting LSB: Kernel based NFS Daemon and SuSEfirewall2 Create Excessive Delays in Nominal Boot Times Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: secure@aphofis.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 May need reassignment to X.org...Not sure of What Component Classification to use at All???? :-) During normal boot there are two huge delays the first greater than 100 seconds the second greater than 45 seconds that slow a normal fast boot to be back as slow prior to LSB and UDEV. During my 3 x X_64 PC's boot standard boot from HDD the script stalls for greater than 100 second on my very powerful hardware. The first is LSB: start the kernel based NFS daemon... This takes longer than 100 second The second is LSB: start SuSEfirewall2... This takes longer than 45 seconds and all my X_64 Quad Core running above 3400 clicks with huge amounts of well resourced Video CPU and RAM and System RAM. Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: I would expect that a Daemon should load without any delays if indead we are just starting more daemons to run Kernel based functions. I can sort of understand NFS as it seems I'm the only one in the world to use NFS; but stage two of SuSEfirewall taking up to 45 seconds is nuts. Both modules should just load one after another despite existence of NFS and Firewall entries and or exceptions. Obviously you are going to need log files and I have 3 x X64 PC's that all exhibit this issue so could you be most clear about the log files you need and well take this one PC at a time if thats o.k with you -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c1
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c
Jiri Srain
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c
Xiyuan Liu
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c2
--- Comment #2 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c3
Steffen Winterfeldt
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c4
--- Comment #4 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c5
Neil Brown
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c6
--- Comment #6 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c7
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c8
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c9
--- Comment #9 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c10
--- Comment #10 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c11
--- Comment #11 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c12
--- Comment #12 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c13
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c14
--- Comment #14 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c15
--- Comment #15 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c16
--- Comment #16 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c17
--- Comment #17 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c18
--- Comment #18 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c19
--- Comment #19 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c20
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c22
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c23
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c24
--- Comment #24 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c25
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c26
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c27
--- Comment #27 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c28
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c29
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c30
Scott Couston
please try to drop nfs entries from fstab and use autofs if you want them mounted on demand instead of on boot this is supported in openSUSE since ages and is the same in all Linux distributions
I'm not sure firewall is really taking any time but I seem to remember that NFS is not working well together with it, because of using dynamic port numbers so the easiest fix would be to disable the firewall.
Thank you so much! No-one has ever provided details on options of NFS and the world and product would be a better place if they were publicly available. I know you dont want to change Yast but everyone depends on that as they want a GUI. Both of us are happy with editing files and command prompts but the rest of the world just wants to use the product. Personally I hate GUI's but world market demands and depends on them. Users wont touch any product that required manual file edit or command lines. Suggest you change Yast>NFS>Help to include details of demand NFS options 1st. Second would recommend changes to KDE/Gnome control module's to include GUI NFS Auto demand and options. I know this crosses into kde's/Gnome responsibility but to save our product for both Enterprise and open users in the whole world that need Network Share ability NOW via GUI's Our product is so technically better than Windoze starting at our file system. We need to give users a better reason to use Suse Linux that can replace O/S the world over but up to use to give them, at very least, GUI Networking ability! Rather than go off Bugzilla, change classification to 'usability' No more talk WE have to deliver now or give up if only teck people know how to edit files and create shell files to do auto/demand Network share mode. Ideally is must ultimately completely reside in the kernel to run and maintain a dynamic Network share ability.That's means being smart and taking time but once done, its there forever! Can you provide URL for howto and create info that way and just include the same link in Yast>NFS>Help text. I have an outstanding bug just to load local help as being part of default pattern install and have its contents indexable. The product is so wonderful but we keep loosing sight of usability confined to just teck people. RE: Firewall..90 seconds is 90 seconds and the suggestion to a user to stop auto load and load firewall on demand just its commercially acceptable. Agin us tecks can do it but same question..Why should it make any difference to a user 90 seconds is just too long whatever the reasoning. We need to work out the smarts and give users usability in return as no user it going to put up with technical logic...they are to busy just using our product :-) Your thoughts please and keep this alive please and please CC add Jiri's Novell email;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c31
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c32
--- Comment #32 from Scott Couston
As for GUIs, I know of the opposite, which is that for many seriously working people, APIs or CLIs are a must-have and any GUI-only application is useless, because it can not be automated or integrated.
I share your logic very much....Bernhard Will install latest updates and retest. Further I can provide further audit streaming from Significant Hardware Protection that exists well above software firewall as I have many ALG's Filtering of most all TCP Packet information and contents from UDP Packet to assist with Susefirewall analysts. Creating the test data in the first instant will be difficult but what follows subject to suse2 is the easy bit for me. Not sure how I can help with only later analysis available...Please advise if that would assist many thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c33
Scott Couston
btw: bug 863749 could be related, so please install the latest updates and re-test
My apologies for the delay. The Australian financial accounting year is from 31June - 1July. ATM Everyone is preparing the tax for the financial year ending 31 July and just about all .AU is in a holding pattern; especially large companies. Some overseas based companies have a tax year concession and able to report December 31 -1January financial year if their parent company is largely overseas. In the mean time can you please advise version numbers/dates/etc. of both Susefirewall2 and current bug issue re NFS to re-test and supply info for. Placed on NEEDINFO for you so as not to loose continuity and current activity status -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c34
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c35
--- Comment #35 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c36
--- Comment #36 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c37
Scott Couston
I applied the patch from 13.1 on the 12.3 package, so please try this one:
http://download.opensuse.org/update/12.3-test/x86_64/nfs-client-1.2.7-2.22.1...
and tell, whether this works better.
Sorry Bernhard the URL cannot locate a matched object file! Can you please check it for me. I've got another consequence if this but in a reversed role which makes sound logic and actuality! It appears that if the NFS Sever can be located at time of NFS Client boot...Its all good UNTIL I remove the NFS Server. In the absence of the once mounted drive, saving any file to a local drive will timeout to try to re-establish its lost mounter Server_NFS. It can also take in excess of 90 seconds just to save a file in this situation. It's very predicable in reverse order and I'm anxious to get the right logs to you as anything Kernel based has sometimes so much testing to be done! I've changed to NEEDINFO for you Cheers -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c38
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c39
--- Comment #39 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c40
--- Comment #40 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c41
--- Comment #41 from Scott Couston
This long hanging is to be expected and normal. There are only two ways to handle this case of connection loss selected via fstab mount options: hard: wait forever until the server returns soft: give up and return an error to the application
I think, the file-not-found error is because the update was now released so you should get it with zypper up nfs-client
I have taken a very outside look at what we ship by default. We provide NFS Services via via Yast with great ease so the default we ship is the root of our problems. I think its better to ship NFS services as we do but using the default of soft rather than our current wait forever. Here's where your overview of the project's perspective development comes in. Sharing Network drives is fundamental and everyone expects it to just work. Network share's are now mandatory not 'a like to have option' when people buy Enterprise or use Open. Yes I can hear you in the background...but with Enterprise there is most certainly Netware File Services available but until we have a Linux based Netware File Server we'd better get our own house in order. Can we simply ship NFS Services via the API to use the soft option. There must be a disadvantage there somewhere. Asking people to go from NFS Services API and put them in the 'Partitioner' is the most frightening thought I could. imagine. The reason I pushed to kernel based NFS services should not be from the point of just retrying the mount or dismount command via the scheduler. If our kernel based NFS services cant just sit there in perpetuity watching network services appear or disappear from the other PC's that join or shutdown; we need a rethink on how we apply this to the kernel. As we both discussed the loss of a once associated NFS Client Server relationship and you remove its server by downing the PC; simply saving a file is 90 seconds in delay! This is where I have the luxury of saying this is not commercially acceptable so lets toss the idea of managing NFS by the kernel that doesn’t cause any delay. Spending 90 second delay in saving a file is just not happening in a viable alt O/S...We have got to get smart so lets get a few more dynamic idea together as what we are currently doing isn’t happening well! Your serve :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c42
Scott Couston
From what I understand of this log, the kernel boys are giving me a 90 second grace period for NFS services Soft: Option or not, no matter what.
We don't need a grace period of devices to be or not be there at time of boot. Waiting for a HDD to come online at boot is perfectly ok but my logic is NFS services are either there or not there at boot. I dont thing we want to offer a 90 second grace period just because NFS Services are config at all but thanks to the kernel boys anyway.Adding + 90 secons to boot each PC and my coffee is made but now also gone cold of me! My whole logic is if we are going to move NFS Services to be handled by the kernel, NFS drives mount and dismount should be a constant dynamic process transparent to the user, no delay. We seem to be stuck half way in starting services sure but they shouldn’t include NFS. We've got part of NFS Services is the kernel which should simply pass any future dynamic mount's dis-mount’s to the scheduler to keep ever watching for. No one wants to wait + 90 seconds just to boot a PC just to see if NFS Services appear. Nor does anyone want to wait 90 seconds to save a local file, if at that time, NFS Services are not longer present. I might have this log interpreted all wrong and I really hope I do! Bernhard, please tell me I've got it all wrong and my logic is stupid???? 2014-06-22T13:30:28.780029+10:00 multivac010 bluetoothd[1894]: Bluetooth daemon 4.101 2014-06-22T13:30:28.796237+10:00 multivac010 dbus-daemon[693]: dbus[693]: [system] Successfully activated service 'org.bluez' 2014-06-22T13:30:28.796462+10:00 multivac010 dbus[693]: [system] Successfully activated service 'org.bluez' 2014-06-22T13:30:28.796617+10:00 multivac010 bluetoothd[1894]: Starting SDP server 2014-06-22T13:30:28.796794+10:00 multivac010 bluetoothd[1894]: bluetoothd[1894]: Starting SDP server 2014-06-22T13:30:28.796955+10:00 multivac010 systemd[1]: Started Bluetooth service. 2014-06-22T13:30:29.049681+10:00 multivac010 kernel: [ 142.649087] Bluetooth: Core ver 2.16 2014-06-22T13:30:29.049704+10:00 multivac010 kernel: [ 142.649110] NET: Registered protocol family 31 2014-06-22T13:30:29.049705+10:00 multivac010 kernel: [ 142.649111] Bluetooth: HCI device and connection manager initialized 2014-06-22T13:30:29.049707+10:00 multivac010 kernel: [ 142.649120] Bluetooth: HCI socket layer initialized 2014-06-22T13:30:29.049708+10:00 multivac010 kernel: [ 142.649121] Bluetooth: L2CAP socket layer initialized 2014-06-22T13:30:29.049709+10:00 multivac010 kernel: [ 142.649125] Bluetooth: SCO socket layer initialized 2014-06-22T13:30:29.324525+10:00 multivac010 bluetoothd[1894]: bluetoothd[1894]: Parsing /etc/bluetooth/input.conf failed: No such file or directory 2014-06-22T13:30:29.324673+10:00 multivac010 kernel: [ 142.923113] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 2014-06-22T13:30:29.324686+10:00 multivac010 kernel: [ 142.923116] Bluetooth: BNEP filters: protocol multicast 2014-06-22T13:30:29.324687+10:00 multivac010 kernel: [ 142.923124] Bluetooth: BNEP socket layer initialized 2014-06-22T13:30:29.324782+10:00 multivac010 bluetoothd[1894]: bluetoothd[1894]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory 2014-06-22T13:30:29.324985+10:00 multivac010 bluetoothd[1894]: bluetoothd[1894]: Bluetooth Management interface initialized 2014-06-22T13:30:29.325159+10:00 multivac010 bluetoothd[1894]: Parsing /etc/bluetooth/input.conf failed: No such file or directory 2014-06-22T13:30:29.325321+10:00 multivac010 bluetoothd[1894]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory 2014-06-22T13:30:29.325471+10:00 multivac010 bluetoothd[1894]: Bluetooth Management interface initialized 2014-06-22T13:30:29.913007+10:00 multivac010 rtkit-daemon[1876]: Successfully made thread 1912 of process 1912 (/usr/bin/pulseaudio) owned by 'scott' high priority at nice level -11. 2014-06-22T13:30:29.913220+10:00 multivac010 rtkit-daemon[1876]: Supervising 5 threads of 2 processes of 1 users. 2014-06-22T13:30:29.913540+10:00 multivac010 pulseaudio[1912]: [pulseaudio] pid.c: Daemon already running. 2014-06-22T13:30:30.265412+10:00 multivac010 rtkit-daemon[1876]: Successfully made thread 1935 of process 1935 (/usr/bin/pulseaudio) owned by 'scott' high priority at nice level -11. 2014-06-22T13:30:30.265653+10:00 multivac010 rtkit-daemon[1876]: Supervising 5 threads of 2 processes of 1 users. 2014-06-22T13:30:30.265834+10:00 multivac010 pulseaudio[1935]: [pulseaudio] pid.c: Daemon already running. 2014-06-22T13:30:31.273238+10:00 multivac010 systemd[1]: Mounting FUSE Control File System... 2014-06-22T13:30:31.273674+10:00 multivac010 kernel: [ 144.866156] fuse init (API version 7.20) 2014-06-22T13:30:31.276139+10:00 multivac010 systemd[1]: Mounted FUSE Control File System. 2014-06-22T13:30:32.293685+10:00 multivac010 kernel: [ 145.883262] svc: 192.168.1.30, port=743: unknown version (4 for prog 100003, nfsd) 2014-06-22T13:30:32.325096+10:00 multivac010 rpc.mountd[1305]: refused mount request from 192.168.1.30 for /scott_server (/scott_server): unmatched host 2014-06-22T13:30:32.334677+10:00 multivac010 kernel: [ 145.924878] svc: 192.168.1.30, port=703: unknown version (4 for prog 100003, nfsd) 2014-06-22T13:30:32.336400+10:00 multivac010 rpc.mountd[1305]: refused mount request from 192.168.1.30 for /home/scott (/home/scott): unmatched host 2014-06-22T13:30:32.403680+10:00 multivac010 kernel: [ 145.992851] svc: 192.168.1.30, port=914: unknown version (4 for prog 100003, nfsd) 2014-06-22T13:30:32.404605+10:00 multivac010 rpc.mountd[1305]: refused mount request from 192.168.1.30 for /home/scott (/home/scott): unmatched host 2014-06-22T13:30:32.414667+10:00 multivac010 kernel: [ 146.004650] svc: 192.168.1.30, port=765: unknown version (4 for prog 100003, nfsd) 2014-06-22T13:30:32.417074+10:00 multivac010 rpc.mountd[1305]: refused mount request from 192.168.1.30 for /scott_server (/scott_server): unmatched host 2014-06-22T13:30:40.300236+10:00 multivac010 rtkit-daemon[1876]: Successfully made thread 2020 of process 2020 (/usr/bin/pulseaudio) owned by 'scott' high priority at nice level -11. 2014-06-22T13:30:40.300468+10:00 multivac010 rtkit-daemon[1876]: Supervising 5 threads of 2 processes of 1 users. 2014-06-22T13:30:40.300673+10:00 multivac010 pulseaudio[2020]: [pulseaudio] pid.c: Daemon already running. 2014-06-22T13:30:55.350708+10:00 multivac010 polkitd[1716]: Registered Authentication Agent for unix-session:2 (system bus name :1.48 [/usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) 2014-06-22T13:32:08.352402+10:00 multivac010 dbus-daemon[693]: dbus[693]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) 2014-06-22T13:32:08.352819+10:00 multivac010 dbus[693]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) 2014-06-22T13:32:08.712077+10:00 multivac010 dbus-daemon[693]: dbus[693]: [system] Successfully activated service 'org.freedesktop.PackageKit' 2014-06-22T13:32:08.712100+10:00 multivac010 dbus[693]: [system] Successfully activated service 'org.freedesktop.PackageKit' 2014-06-22T13:32:43.647284+10:00 multivac010 dbus-daemon[693]: dbus[693]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) 2014-06-22T13:32:43.647632+10:00 multivac010 dbus[693]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) 2014-06-22T13:32:43.651475+10:00 multivac010 dbus-daemon[693]: no kernel backlight interface found 2014-06-22T13:32:43.659740+10:00 multivac010 dbus-daemon[693]: dbus[693]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' 2014-06-22T13:32:43.659997+10:00 multivac010 dbus[693]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' 2014-06-22T13:33:58.646547+10:00 multivac010 dbus-daemon[693]: dbus[693]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) 2014-06-22T13:33:58.647016+10:00 multivac010 dbus[693]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) 2014-06-22T13:33:58.650845+10:00 multivac010 dbus-daemon[693]: no kernel backlight interface found 2014-06-22T13:33:58.659203+10:00 multivac010 dbus-daemon[693]: dbus[693]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' 2014-06-22T13:33:58.659415+10:00 multivac010 dbus[693]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' 2014-06-22T13:34:18.057719+10:00 multivac010 kernel: [ 371.011108] svc: 192.168.1.30, port=732: unknown version (4 for prog 100003, nfsd) 2014-06-22T13:34:18.087595+10:00 multivac010 rpc.mountd[1305]: refused mount request from 192.168.1.30 for /scott_server (/scott_server): unmatched host 2014-06-22T13:34:18.089689+10:00 multivac010 kernel: [ 371.043224] svc: 192.168.1.30, port=706: unknown version (4 for prog 100003, nfsd) 2014-06-22T13:34:18.090892+10:00 multivac010 rpc.mountd[1305]: refused mount request from 192.168.1.30 for /home/scott (/home/scott): unmatched host 2014-06-22T13:35:13.647694+10:00 multivac010 dbus-daemon[693]: dbus[693]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) 2014-06-22T13:35:13.648004+10:00 multivac010 dbus[693]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) 2014-06-22T13:35:13.651911+10:00 multivac010 dbus-daemon[693]: no kernel backlight interface found 2014-06-22T13:35:13.660323+10:00 multivac010 dbus-daemon[693]: dbus[693]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' 2014-06-22T13:35:13.660534+10:00 multivac010 dbus[693]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' 2014-06-22T13:35:27.479719+10:00 multivac010 dbus-daemon[693]: dbus[693]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) 2014-06-22T13:35:27.479821+10:00 multivac010 dbus[693]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) 2014-06-22T13:35:27.484529+10:00 multivac010 dbus-daemon[693]: no kernel backlight interface found 2014-06-22T13:35:27.492648+10:00 multivac010 dbus-daemon[693]: dbus[693]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' 2014-06-22T13:35:27.492877+10:00 multivac010 dbus[693]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' 2014-06-22T13:35:41.725869+10:00 multivac010 su: (to root) scott on /dev/pts/2 2014-06-22T13:35:41.726112+10:00 multivac010 su: pam_unix(su:session): session opened for user root by (uid=1000) 2014-06-22T13:35:41.771977+10:00 multivac010 su: pam_unix(su:session): session closed for user root 2014-06-22T13:35:41.889706+10:00 multivac010 su: (to root) scott on /dev/pts/2 2014-06-22T13:35:41.890025+10:00 multivac010 su: pam_unix(su:session): session opened for user root by (uid=1000) 2014-06-22T13:36:28.819219+10:00 multivac010 systemd[1]: Stopping LSB: Start the kernel based NFS daemon... 2014-06-22T13:36:28.844700+10:00 multivac010 kernel: [ 501.429517] nfsd: last server has exited, flushing export cache 2014-06-22T13:36:28.966662+10:00 multivac010 rpc.mountd[1305]: Caught signal 15, un-registering and exiting. 2014-06-22T13:36:29.037147+10:00 multivac010 nfsserver[2339]: Shutting down kernel based NFS server: nfsd statd mountd..done 2014-06-22T13:36:29.042804+10:00 multivac010 systemd[1]: Stopped LSB: Start the kernel based NFS daemon. 2014-06-22T13:36:29.053736+10:00 multivac010 systemd[1]: Starting LSB: Start the kernel based NFS daemon... 2014-06-22T13:36:29.089393+10:00 multivac010 rpc.mountd[2378]: Version 1.2.7 starting 2014-06-22T13:36:29.096345+10:00 multivac010 rpc.statd[2381]: Version 1.2.7 starting 2014-06-22T13:36:29.096577+10:00 multivac010 rpc.statd[2381]: Flags: TI-RPC 2014-06-22T13:36:29.116691+10:00 multivac010 kernel: [ 501.700725] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory 2014-06-22T13:36:29.116705+10:00 multivac010 kernel: [ 501.700736] NFSD: starting 90-second grace period 2014-06-22T13:36:29.116900+10:00 multivac010 sm-notify[2390]: Version 1.2.7 starting 2014-06-22T13:36:29.117190+10:00 multivac010 nfsserver[2359]: Starting kernel based NFS server: mountd statd nfsd sm-notify..done 2014-06-22T13:36:29.117571+10:00 multivac010 systemd[1]: Started LSB: Start the kernel based NFS daemon. 2014-06-22T13:36:31.368789+10:00 multivac010 su: pam_unix(su:session): session closed for user root 2014-06-22T13:36:49.263823+10:00 multivac010 su: (to root) scott on /dev/pts/2 2014-06-22T13:36:49.264064+10:00 multivac010 su: pam_unix(su:session): session opened for user root by (uid=1000) 2014-06-22T13:36:49.269307+10:00 multivac010 su: pam_unix(su:session): session closed for user root 2014-06-22T13:36:49.386650+10:00 multivac010 su: (to root) scott on /dev/pts/2 2014-06-22T13:36:49.386964+10:00 multivac010 su: pam_unix(su:session): session opened for user root by (uid=1000) 2014-06-22T13:36:53.091680+10:00 multivac010 kernel: [ 525.608768] device-mapper: uevent: version 1.0.3 2014-06-22T13:36:53.091703+10:00 multivac010 kernel: [ 525.608820] device-mapper: ioctl: 4.23.0-ioctl (2012-07-25) initialised: dm-devel@redhat.com 2014-06-22T13:36:54.097682+10:00 multivac010 kernel: [ 526.611370] st: Version 20101219, fixed bufsize 32768, s/g segs 256 2014-06-22T13:36:54.152683+10:00 multivac010 kernel: [ 526.666532] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found 2014-06-22T13:36:54.152702+10:00 multivac010 kernel: [ 526.666535] EDD information not available. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c43
--- Comment #43 from Neil Brown
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c44
Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c45
--- Comment #45 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c46
--- Comment #46 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c47
--- Comment #47 from Scott Couston
https://bugzilla.novell.com/show_bug.cgi?id=856916
https://bugzilla.novell.com/show_bug.cgi?id=856916#c48
Scott Couston
participants (1)
-
bugzilla_noreply@novell.com