Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Error message in the system log: "failed to read service info "

  1. #1

    Default Error message in the system log: "failed to read service info "

    Hi there,

    after 1/2 a year of OpenSuse I have several problems on my PC.

    Amongst them is a log spammer:
    2014-03-06T14:58:39.143197+01:00 Hasty rpc.gssd[748]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-06T14:58:39.143490+01:00 Hasty rpc.gssd[748]: ERROR: failed to read service info
    2014-03-06T14:58:39.143670+01:00 Hasty rpc.gssd[748]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-06T14:58:39.143846+01:00 Hasty rpc.gssd[748]: ERROR: failed to read service info
    2014-03-06T14:58:39.144117+01:00 Hasty rpc.gssd[748]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-06T14:58:39.144412+01:00 Hasty rpc.gssd[748]: ERROR: failed to read service info
    2014-03-06T14:58:39.144731+01:00 Hasty rpc.gssd[748]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-06T14:58:39.145042+01:00 Hasty rpc.gssd[748]: ERROR: failed to read service info
    Had updated from 12.3 to 13.1 about two month ago.
    It creates at least 30 to 40 lines with the above content. No idea where this comes from.
    Anyone ?

    TIA , Joe

  2. #2
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Error message in the system log: "failed to read service info"

    On 2014-03-06 15:26, J0Eeoj wrote:
    >
    > Hi there,
    >
    > after 1/2 a year of OpenSuse I have several problems on my PC.
    >
    > Amongst them is a log spammer:


    Just a comment: please use code tags for printouts and commands (the '#'
    button in the forum editor). See
    photo


    Code:
    
    >  2014-03-06T14:58:39.143197+01:00 Hasty rpc.gssd[748]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    > 2014-03-06T14:58:39.143490+01:00 Hasty rpc.gssd[748]: ERROR: failed to read service info
    There is a man page for rpc.gssd that explains a bit what it is.

    You could try and see if the file
    "/var/lib/nfs/rpc_pipefs/gssd/clntXX/gssd" does exist or not.


    > Had updated from 12.3 to 13.1 about two month ago.


    What method did you use? Online upgrade or offline upgrade?

    Online upgrade
    method
    Offline
    upgrade method


    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

  3. #3

    Default Re: Error message in the system log: "failed to read service info "

    HI, thanks for your answer.

    "/var/lib/nfs/rpc_pipefs/gssd/clntXX/gssd" does exist.

    I used the update method provided with on 13.1 64bit DVD and it seemed to run without problems.

    Cheers, Joe

  4. #4
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Error message in the system log: "failed to read service info"

    On 2014-03-13 08:26, J0Eeoj wrote:
    >
    > HI, thanks for your answer.
    >
    > "/var/lib/nfs/rpc_pipefs/gssd/clntXX/gssd" does exist.
    >
    > I used the update method provided with on 13.1 64bit DVD and it seemed
    > to run without problems.


    That's the offline method. I use it, but it has a problem: the DVD is
    too small to contain everything, so not everything is updated.

    You have to run after it completes, this:

    Code:
    zypper dup
    zypper up
    zypper patch
    Make sure you only have the 4 official repos active before running that.
    Then, verify:

    Upgrading rpm query

    Code:
    rpm -q -a --queryformat "%{INSTALLTIME};%{INSTALLTIME:day}; \
    %{BUILDTIME:day}; %{NAME};%{VERSION}-%-7{RELEASE};%{arch}; \
    %{VENDOR};%{PACKAGER};%{DISTRIBUTION};%{DISTTAG}\n" \
    | sort | cut --fields="2-" --delimiter=\; \
    | tee rpmlist.csv | less -S
    
    or
    
    rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \
    %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \
    %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \
    | sort | cut --fields="2-" | tee rpmlist | less -S
    or

    rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \
    %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \
    %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \
    | sort | cut --fields="2-" | tee rpmlist \
    | egrep -v "openSUSE.12\.3" | less -S

    (not containing 12.3)


    With that query, you find listed at the top old packages that may have
    to be upgraded manually, because they belong to the previous release, or
    perhaps came from extra repositories and no equivalent was found in the
    active repos. In that case you have to start at this phase to add the
    needed extra repositories and update those packages.

    Many of them show in red in YaST,



    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

  5. #5

    Default Re: Error message in the system log: "failed to read service info "

    Hi Carlos,

    thanks for the help. Did the update via Zypper and got quite a number of updates. Afterwards Google Earth is running again, but Temaviewer still does not run (even after reinstall) and I switched off NSFv4 support, which uses rpc.gssd, thus I expecte that these ERROR lines would disapear, but they are still there.
    I took some time into copying my last boot sequence from the system log into an editor to make it easier to read and select sequences which look unusal in my eyes: :

    Code:
    ...
    2014-03-14T13:53:16.773232+01:00 Hasty kernel: [    0.000000] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20130517/tbfadt-603)
    ...
    2014-03-14T13:53:16.773246+01:00 Hasty kernel: [    0.000000] Faking a node at [mem 0x0000000000000000-0x000000043effffff]
    ...
    2014-03-14T13:53:16.773598+01:00 Hasty kernel: [    0.512175] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130517/hwxface-571)
    2014-03-14T13:53:16.773601+01:00 Hasty kernel: [    0.512178] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
    ...
    2014-03-14T13:53:16.773613+01:00 Hasty kernel: [    0.535141] acpi PNP0A03:00: ACPI _OSC support notification failed, disabling PCIe ASPM
    2014-03-14T13:53:16.773613+01:00 Hasty kernel: [    0.535143] acpi PNP0A03:00: Unable to request _OSC control (_OSC support mask: 0x08)
    ...
    2014-03-14T13:53:17.014923+01:00 Hasty dbus[539]: [system] Successfully activated service 'org.bluez'
    2014-03-14T13:53:17.015914+01:00 Hasty systemd[1]: Started Bluetooth service.
    2014-03-14T13:53:17.017311+01:00 Hasty rpc.gssd[745]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory (The path exists, but only the file gssd exists but not info in the subdir and I am not allowed to create one. Changed the rights, but was not allowed to write into the subdir. Virtual ?)
    2014-03-14T13:53:17.017663+01:00 Hasty rpc.gssd[745]: ERROR: failed to read service info
    2014-03-14T13:53:17.020059+01:00 Hasty nfs[652]: Starting NFS client services: sm-notify gssd..done
    2014-03-14T13:53:17.022206+01:00 Hasty bluetoothd[743]: Starting SDP server
    2014-03-14T13:53:17.024503+01:00 Hasty kernel: [    5.531230] Bluetooth: Core ver 2.16  (I have no bluetooth on my PC - strange)
    2014-03-14T13:53:17.024510+01:00 Hasty kernel: [    5.531248] NET: Registered protocol family 31
    2014-03-14T13:53:17.024511+01:00 Hasty kernel: [    5.531250] Bluetooth: HCI device and connection manager initialized
    2014-03-14T13:53:17.024512+01:00 Hasty kernel: [    5.531258] Bluetooth: HCI socket layer initialized
    2014-03-14T13:53:17.024513+01:00 Hasty kernel: [    5.531260] Bluetooth: L2CAP socket layer initialized
    2014-03-14T13:53:17.024514+01:00 Hasty kernel: [    5.531265] Bluetooth: SCO socket layer initialized
    2014-03-14T13:53:17.024515+01:00 Hasty kernel: [    5.533452] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    2014-03-14T13:53:17.024515+01:00 Hasty kernel: [    5.533454] Bluetooth: BNEP filters: protocol multicast
    2014-03-14T13:53:17.024516+01:00 Hasty kernel: [    5.533461] Bluetooth: BNEP socket layer initialized
    2014-03-14T13:53:17.026740+01:00 Hasty bluetoothd[743]: Bluetooth management interface 1.3 initialized 
    2014-03-14T13:53:17.027044+01:00 Hasty dbus[539]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
    2014-03-14T13:53:17.027346+01:00 Hasty systemd[1]: Starting Hostname Service...
    2014-03-14T13:53:17.029577+01:00 Hasty dbus[539]: [system] Successfully activated service 'org.freedesktop.hostname1'
    2014-03-14T13:53:17.030365+01:00 Hasty systemd[1]: Started Hostname Service.
    2014-03-14T13:53:17.037918+01:00 Hasty kernel: [    5.546677] NFS: Registering the id_resolver key type
    2014-03-14T13:53:17.037930+01:00 Hasty kernel: [    5.546691] Key type id_resolver registered
    2014-03-14T13:53:17.037931+01:00 Hasty kernel: [    5.546692] Key type id_legacy registered
    2014-03-14T13:53:17.037841+01:00 Hasty rpc.gssd[745]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-14T13:53:17.038261+01:00 Hasty rpc.gssd[745]: ERROR: failed to read service info
    2014-03-14T13:53:17.038579+01:00 Hasty rpc.gssd[745]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-14T13:53:17.038848+01:00 Hasty rpc.gssd[745]: ERROR: failed to read service info
    2014-03-14T13:53:17.039124+01:00 Hasty rpc.gssd[745]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-14T13:53:17.039393+01:00 Hasty rpc.gssd[745]: ERROR: failed to read service info
    2014-03-14T13:53:17.039661+01:00 Hasty rpc.gssd[745]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-14T13:53:17.039912+01:00 Hasty rpc.gssd[745]: ERROR: failed to read service info
    2014-03-14T13:53:17.040160+01:00 Hasty rpc.gssd[745]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-14T13:53:17.040386+01:00 Hasty rpc.gssd[745]: ERROR: failed to read service info2014-03-14T13:53:17.015914+01:00 Hasty systemd[1]: Started Bluetooth service.
    2014-03-14T13:53:17.017311+01:00 Hasty rpc.gssd[745]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-14T13:53:17.017663+01:00 Hasty rpc.gssd[745]: ERROR: failed to read service info
    2014-03-14T13:53:17.020059+01:00 Hasty nfs[652]: Starting NFS client services: sm-notify gssd..done
    2014-03-14T13:53:17.022206+01:00 Hasty bluetoothd[743]: Starting SDP server
    2014-03-14T13:53:17.024503+01:00 Hasty kernel: [    5.531230] Bluetooth: Core ver 2.16
    2014-03-14T13:53:17.024510+01:00 Hasty kernel: [    5.531248] NET: Registered protocol family 31
    2014-03-14T13:53:17.024511+01:00 Hasty kernel: [    5.531250] Bluetooth: HCI device and connection manager initialized
    2014-03-14T13:53:17.024512+01:00 Hasty kernel: [    5.531258] Bluetooth: HCI socket layer initialized
    2014-03-14T13:53:17.024513+01:00 Hasty kernel: [    5.531260] Bluetooth: L2CAP socket layer initialized
    2014-03-14T13:53:17.024514+01:00 Hasty kernel: [    5.531265] Bluetooth: SCO socket layer initialized
    2014-03-14T13:53:17.024515+01:00 Hasty kernel: [    5.533452] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    2014-03-14T13:53:17.024515+01:00 Hasty kernel: [    5.533454] Bluetooth: BNEP filters: protocol multicast
    2014-03-14T13:53:17.024516+01:00 Hasty kernel: [    5.533461] Bluetooth: BNEP socket layer initialized
    2014-03-14T13:53:17.026740+01:00 Hasty bluetoothd[743]: Bluetooth management interface 1.3 initialized
    2014-03-14T13:53:17.027044+01:00 Hasty dbus[539]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
    2014-03-14T13:53:17.027346+01:00 Hasty systemd[1]: Starting Hostname Service...
    2014-03-14T13:53:17.029577+01:00 Hasty dbus[539]: [system] Successfully activated service 'org.freedesktop.hostname1'
    2014-03-14T13:53:17.030365+01:00 Hasty systemd[1]: Started Hostname Service.
    2014-03-14T13:53:17.037918+01:00 Hasty kernel: [    5.546677] NFS: Registering the id_resolver key type
    2014-03-14T13:53:17.037930+01:00 Hasty kernel: [    5.546691] Key type id_resolver registered
    2014-03-14T13:53:17.037931+01:00 Hasty kernel: [    5.546692] Key type id_legacy registered
    2014-03-14T13:53:17.037841+01:00 Hasty rpc.gssd[745]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-14T13:53:17.038261+01:00 Hasty rpc.gssd[745]: ERROR: failed to read service info
    2014-03-14T13:53:17.038579+01:00 Hasty rpc.gssd[745]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    "    "    "    "    "    "    "    "    "    "    "
    2014-03-14T13:53:17.043531+01:00 Hasty rpc.gssd[745]: ERROR: failed to read service info
    2014-03-14T13:53:17.043807+01:00 Hasty rpc.gssd[745]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-14T13:53:17.044119+01:00 Hasty rpc.gssd[745]: ERROR: failed to read service info
    2014-03-14T13:53:17.045255+01:00 Hasty nfs[652]: Mounting network file systems ...mount.nfs: mount system call failed
    2014-03-14T13:53:17.045656+01:00 Hasty rpc.gssd[745]: ERROR: unable to resolve 192.168.2.200 to hostname: Name or service not known
    2014-03-14T13:53:17.047199+01:00 Hasty rpc.gssd[745]: ERROR: failed to read service info
    2014-03-14T13:53:17.047393+01:00 Hasty rpc.gssd[745]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-14T13:53:17.047581+01:00 Hasty rpc.gssd[745]: ERROR: failed to read service info
    2014-03-14T13:53:17.047767+01:00 Hasty rpc.gssd[745]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    "    "    "    "    "    "    "    "    "    "    "
    2014-03-14T13:53:17.063433+01:00 Hasty rpc.gssd[745]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    2014-03-14T13:53:17.063712+01:00 Hasty rpc.gssd[745]: ERROR: failed to read service info
    2014-03-14T13:53:17.064107+01:00 Hasty nfs[652]: mount.nfs: mount system call failed
    2014-03-14T13:53:17.064314+01:00 Hasty systemd[1]: Started LSB: NFS client services.
    ...
    2014-03-14T13:53:23.316591+01:00 Hasty systemd: pam_unix(systemd-user:session): session opened for user joe by (uid=0)
    2014-03-14T13:53:23.321682+01:00 Hasty systemd[1171]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory (Indeed /run/user/1000/dbus does not exist)
    2014-03-14T13:53:23.336533+01:00 Hasty systemd[1171]: Mounted /sys/fs/fuse/connections.
    ...
    2014-03-14T13:53:23.669164+01:00 Hasty checkproc: checkproc: can not get session id for process 1320!
    ...
    Any idea whats going on there ?

    TIA, Joe

  6. #6
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Error message in the system log: "failed to read service info"

    On 2014-03-14 14:46, J0Eeoj wrote:
    >
    > Hi Carlos,
    >
    > thanks for the help. Did the update via Zypper and got quite a number of
    > updates. Afterwards Google Earth is running again, but Temaviewer still
    > does not run (even after reinstall) and I switched off NSFv4 support,
    > which uses rpc.gssd, thus I expecte that these ERROR lines would
    > disapear, but they are still there.



    I searched my log, and I found some with the "/var/lib/nfs/rpc_pipefs"
    string:

    Code:
    
    > /var/log/messages-20131205.xz:<3.4> 2013-11-28 22:07:43 Telcontar rpc.idmapd 3214 - -  dirscancb: open(/var/lib/nfs/rpc_pipefs/nfs/clnt96): No such file or directory
    > /var/log/messages-20131205.xz:<3.4> 2013-12-01 22:39:32 Telcontar rpc.idmapd 3214 - -  dirscancb: open(/var/lib/nfs/rpc_pipefs/nfs/clntb2): No such file or directory
    > /var/log/messages-20131205.xz:<3.6> 2013-12-04 20:38:19 Telcontar nfs 24263 - -  Shutting down NFS client services:umount: /var/lib/nfs/rpc_pipefs: target is busy.
    > /var/log/messages-20140123.xz:<3.4> 2013-12-18 22:58:54 Telcontar rpc.idmapd 3337 - -  dirscancb: open(/var/lib/nfs/rpc_pipefs/nfs/clnt53): No such file or directory
    Too few to be important, in my case. I do see your same error on another
    machine, though, which uses NFS as client (the other one acts as server):

    Code:
    
    > 2014-03-14T04:36:14.201583+01:00 AmonLanc sm-notify[1689]: Version 1.2.8 starting
    > 2014-03-14T04:36:14.231115+01:00 AmonLanc kernel: [   55.125972] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    > 2014-03-14T04:36:14.337090+01:00 AmonLanc rpc.gssd[1719]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory    ********
    > 2014-03-14T04:36:14.338415+01:00 AmonLanc rpc.gssd[1719]: ERROR: failed to read service info
    > 2014-03-14T04:36:14.370333+01:00 AmonLanc nfs[1659]: Starting NFS client services: sm-notify gssd idmapd..done
    > 2014-03-14T04:36:14.370822+01:00 AmonLanc systemd[1]: Started LSB: NFS client services.
    > 2014-03-14T04:36:14.372258+01:00 AmonLanc systemd[1]: Starting Remote File Systems (Pre).
    > 2014-03-14T04:36:14.378377+01:00 AmonLanc systemd[1]: Reached target Remote File Systems (Pre).
    > 2014-03-14T04:36:14.379968+01:00 AmonLanc systemd[1]: Starting Remote File Systems.
    > 2014-03-14T04:36:14.392406+01:00 AmonLanc systemd[1]: Reached target Remote File Systems.
    > 2014-03-14T04:36:14.396215+01:00 AmonLanc systemd[1]: Starting LSB: SUSE Meta PPP Daemon...
    > 2014-03-14T04:36:14.405473+01:00 AmonLanc systemd[1]: Starting LSB: Network time protocol daemon (ntpd)...
    > 2014-03-14T04:36:14.424510+01:00 AmonLanc systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
    > 2014-03-14T04:36:14.516925+01:00 AmonLanc rpc.mountd[1743]: Version 1.2.8 starting
    > 2014-03-14T04:36:14.525211+01:00 AmonLanc systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
    > 2014-03-14T04:36:14.527360+01:00 AmonLanc systemd[1]: Starting Permit User Sessions...
    > 2014-03-14T04:36:14.566676+01:00 AmonLanc rpc.statd[1759]: Version 1.2.8 starting
    > 2014-03-14T04:36:14.567787+01:00 AmonLanc rpc.statd[1759]: Flags: TI-RPC
    > 2014-03-14T04:36:14.633326+01:00 AmonLanc systemd[1]: Started Permit User Sessions.

    which is only once. But just before that, I rebooted my machine, and I
    had many instances of that message:


    Code:
    
    > 014-03-14T04:09:09.993551+01:00 AmonLanc systemd[1]: Started Cryptography Setup for cr_hoard.
    > 2014-03-14T04:09:10.002178+01:00 AmonLanc systemd[1]: Found device /dev/mapper/cr_hoard.
    > 2014-03-14T04:09:10.007074+01:00 AmonLanc systemd[1]: Starting File System Check on /dev/mapper/cr_hoard...
    > 2014-03-14T04:09:10.078280+01:00 AmonLanc systemd-fsck[11732]: /sbin/fsck.xfs: XFS file system.
    > 2014-03-14T04:09:10.082440+01:00 AmonLanc systemd[1]: Started File System Check on /dev/mapper/cr_hoard.
    > 2014-03-14T04:09:10.083169+01:00 AmonLanc systemd[1]: Mounting /data/hoard...
    > 2014-03-14T04:09:10.093928+01:00 AmonLanc systemd[1]: data-hoard.mount: Directory /data/hoard to mount over is not empty, mounting anyway.
    > 2014-03-14T04:09:10.126530+01:00 AmonLanc kernel: [15376.283187] XFS (dm-0): Mounting Filesystem
    > 2014-03-14T04:09:10.374529+01:00 AmonLanc kernel: [15376.528552] XFS (dm-0): Ending clean mount
    > 2014-03-14T04:09:10.378716+01:00 AmonLanc systemd[1]: Mounted /data/hoard.
    > 2014-03-14T04:09:23.974487+01:00 AmonLanc kernel: [15390.128022] usb 4-2: reset full-speed USB device number 2 using uhci_hcd
    > 2014-03-14T04:09:40.006491+01:00 AmonLanc kernel: [15406.160059] usb 4-2: reset full-speed USB device number 2 using uhci_hcd
    > 2014-03-14T04:10:50.511302+01:00 AmonLanc rpc.gssd[1838]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    > 2014-03-14T04:10:50.512159+01:00 AmonLanc rpc.gssd[1838]: ERROR: failed to read service info
    > 2014-03-14T04:10:50.512743+01:00 AmonLanc rpc.gssd[1838]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    > 2014-03-14T04:10:50.513272+01:00 AmonLanc rpc.gssd[1838]: ERROR: failed to read service info
    > 2014-03-14T04:10:50.513779+01:00 AmonLanc rpc.gssd[1838]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    > 2014-03-14T04:10:50.514280+01:00 AmonLanc rpc.gssd[1838]: ERROR: failed to read service info
    > 2014-03-14T04:10:50.516362+01:00 AmonLanc rpc.gssd[1838]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    > 2014-03-14T04:10:50.517572+01:00 AmonLanc rpc.gssd[1838]: ERROR: failed to read service info
    > 2014-03-14T04:10:50.518821+01:00 AmonLanc rpc.gssd[1838]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    > 2014-03-14T04:10:50.520109+01:00 AmonLanc rpc.gssd[1838]: ERROR: failed to read service info
    > 2014-03-14T04:10:50.521557+01:00 AmonLanc rpc.gssd[1838]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    > 2014-03-14T04:10:50.523013+01:00 AmonLanc rpc.gssd[1838]: ERROR: failed to read service info
    > 2014-03-14T04:10:50.524304+01:00 AmonLanc rpc.gssd[1838]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    > 2014-03-14T04:10:50.525519+01:00 AmonLanc rpc.gssd[1838]: ERROR: failed to read service info
    > 2014-03-14T04:10:50.529821+01:00 AmonLanc rpc.gssd[1838]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    > 2014-03-14T04:10:50.531077+01:00 AmonLanc rpc.gssd[1838]: ERROR: failed to read service info
    > 2014-03-14T04:10:50.532247+01:00 AmonLanc rpc.gssd[1838]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    > 2014-03-14T04:10:50.533469+01:00 AmonLanc rpc.gssd[1838]: ERROR: failed to read service info
    
    
    
    ....
    
    > 2014-03-14T04:10:59.804857+01:00 AmonLanc rpc.gssd[1838]: ERROR: failed to read service info
    > 2014-03-14T04:10:59.806416+01:00 AmonLanc rpc.gssd[1838]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory
    > 2014-03-14T04:10:59.808012+01:00 AmonLanc rpc.gssd[1838]: ERROR: failed to read service info
    > 2014-03-14T04:12:48.178529+01:00 AmonLanc kernel: [15594.333825] perf samples too long (2514 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
    
    and they stop.
    Now, that machine had been hibernated for some days. I moved it to
    another table, reconnecting cables. I had an external disk (encripted)
    mounted via usb, and I moved it over to another socket. The system
    reacted by trying to mount it again. This is probably unrelated.

    Then the rpc messages appear.

    But it is also possible that there was a client side NFS 4 connection
    active prior to hibernation, and in that case, it is quite possible that
    the server was rebooted on the interval.

    Both machines are upgrades from 12.3 to 13.1, offline method.

    However, on another machine, this one upgraded from 11.4 to 13.1, I do
    not see any message with the "rpc.gssd" string, and I use the same NFS
    mount. See, the entries in fstab:


    Code:
    minas-tirith:
    
    > 192.168.1.14:/data/storage_c/repositorios_zypp/ /var/cache/zypp/nfs_packages    nfs     defaults,noauto,_netdev,nfsvers=4       0 0
    > 192.168.1.14:/data/other/                       /mnt/nfs_other                  nfs     defaults,ro,noauto,_netdev,nfsvers=4    0 0
    
    AmonLanc
    
    > telcontar.valinor:/data/storage_c/repositorios_zypp     /var/cache/zypp/nfs_packages    nfs4    noauto,nofail,_netdev 0 0

    Thge machine that has the "problem" does not demand explicit use of nfs
    v4, that's the only relevant different mount option. Well, the problem
    one mounts by name, the other one by IP.

    The problematic one is 32 bit.

    Another person on the mail list reported recently the same error string,
    IIRC.



    So, nothing conclussive.


    > I took some time into copying my last boot sequence from the system log
    > into an editor to make it easier to read and select sequences which
    > look unusal in my eyes: :


    ....


    > Any idea whats going on there ?


    Nope.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

  7. #7

    Default Re: Error message in the system log: "failed to read service info "

    Thanks Carlos,

    I meanwhile experience further problems on my computer. Wine, if started on the command line did start (but not in the KDE GUI), so I tried to start Teamviewer (/opt/teamviwer9/tv_bin/script/teamviewer) by executing it via root console and ... it worked
    Tried to get the pathname of Wine by editing its desktop file and got lots of error messages:
    Code:
    kwrite wine-winecfg.desktop
    kdeinit4: Shutting down running client.
    Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
    kbuildsycoca4 running...
    kbuildsycoca4(1575) KConfigGroup::readXdgListEntry: List entry Keywords in "k3bsetup.desktop" is not compliant with XDG standard (missing trailing semicolon). 
    kbuildsycoca4(1575) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/google-earth.desktop" is not compliant with XDG standard (missing trailing semicolon). 
    kbuildsycoca4(1575) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/google-earth.desktop" is not compliant with XDG standard (missing trailing semicolon). 
    kbuildsycoca4(1575)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/runlevel.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. 
    kbuildsycoca4(1575)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/iscsi-client.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. 
    
    . . . 
    
    kbuildsycoca4(1575)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/inetd.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. 
    QObject::connect: Cannot connect (null)::resourceScoreUpdated(QString, QString, QString, double) to NepomukPlugin::resourceScoreUpdated(QString, QString, QString, double)
    QObject::connect: Cannot connect (null)::recentStatsDeleted(QString, int, QString) to NepomukPlugin::deleteRecentStats(QString, int, QString)
    QObject::connect: Cannot connect (null)::earlierStatsDeleted(QString, int) to NepomukPlugin::deleteEarlierStats(QString, int)
    kactivitymanagerd(1586)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
    QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.7'
    I think there is a problem with the KDE UI. Maybe several versions are mixed up ? Is there a way to reset or repair that thing ?

    Greetings, joe

  8. #8

    Default Re: Error message in the system log: "failed to read service info "

    Quote Originally Posted by J0Eeoj View Post
    Thanks Carlos,

    I meanwhile experience further problems on my computer. Wine, if started on the command line did start (but not in the KDE GUI), so I tried to start Teamviewer (/opt/teamviwer9/tv_bin/script/teamviewer) by executing it via root console and ... it worked
    Tried to get the pathname of Wine by editing its desktop file and got lots of error messages:
    Code:
    kwrite wine-winecfg.desktop
    kdeinit4: Shutting down running client.
    Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
    kbuildsycoca4 running...
    kbuildsycoca4(1575) KConfigGroup::readXdgListEntry: List entry Keywords in "k3bsetup.desktop" is not compliant with XDG standard (missing trailing semicolon). 
    kbuildsycoca4(1575) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/google-earth.desktop" is not compliant with XDG standard (missing trailing semicolon). 
    kbuildsycoca4(1575) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/google-earth.desktop" is not compliant with XDG standard (missing trailing semicolon). 
    kbuildsycoca4(1575)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/runlevel.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. 
    kbuildsycoca4(1575)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/iscsi-client.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. 
    
    . . . 
    
    kbuildsycoca4(1575)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/inetd.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. 
    QObject::connect: Cannot connect (null)::resourceScoreUpdated(QString, QString, QString, double) to NepomukPlugin::resourceScoreUpdated(QString, QString, QString, double)
    QObject::connect: Cannot connect (null)::recentStatsDeleted(QString, int, QString) to NepomukPlugin::deleteRecentStats(QString, int, QString)
    QObject::connect: Cannot connect (null)::earlierStatsDeleted(QString, int) to NepomukPlugin::deleteEarlierStats(QString, int)
    kactivitymanagerd(1586)/nepomuk (library): Could not find virtuoso to connect to. Aborting 
    QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.7'
    I think there is a problem with the KDE UI. Maybe several versions are mixed up ? Is there a way to reset or repair that thing ?
    No. Those messages from kbuildsycoca4 are no errors, just debug messages intended for developers, about flaws/deprecated things in the .desktop files.
    The rest are there because you ran kwrite as root. You don't have to run it as root anyway if you just want to read the wine-winecfg.desktop file.

    You can ignore those messages.

    Regarding wine, how exactly did you try to run it when it didn't work?
    What happens if you type "winecfg" in a terminal window (as user, not root)?
    Last edited by wolfi323; 18-Mar-2014 at 06:18.

  9. #9
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Error message in the system log: "failed to read service info"

    On 2014-03-18 13:56, J0Eeoj wrote:
    >
    > Thanks Carlos,
    >
    > I meanwhile experience further problems on my computer. Wine, if started
    > on the command line did start (but not in the KDE GUI), so I tried to
    > start Teamviewer (/opt/teamviwer9/tv_bin/script/teamviewer) by executing
    > it via root console and ... it worked
    > Tried to get the pathname of Wine by editing its desktop file and got
    > lots of error messages:


    Er... I think you should ask about that in a different thread. If we mix
    two or more so different issues, such as NFS or KDE or Wine, this will
    become a mess.



    > I think there is a problem with the KDE UI. Maybe several versions are
    > mixed up ? Is there a way to reset or repair that thing ?


    You can verify the origin and releases of the packages with an rpm
    query, such as this:

    Code:
    rpm -q -a --queryformat "%{INSTALLTIME};%{INSTALLTIME:day}; \
    %{BUILDTIME:day}; %{NAME};%{VERSION}-%-7{RELEASE};%{arch}; \
    %{VENDOR};%{PACKAGER};%{DISTRIBUTION};%{DISTTAG}\n" \
    | sort | cut --fields="2-" --delimiter=\; \
    | tee rpmlist.csv | less -S
    
    or
    
    rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \
    %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \
    %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \
    | sort | cut --fields="2-" | tee rpmlist | less -S
    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

  10. #10

    Default Re: Error message in the system log: "failed to read service info "

    Hi Carlos, hi Wolfi323,

    tried those commands Carlos suggested and everything is OS13.1 , thus I assume it's ok.

    I also tried as you ,Wolfi, mentioned and got :
    Code:
    joe@Hasty:~> winecfg
    wine: '/tmp/.wine-1000/server-807-140155' must not be accessible by other users
    As one can see I did this as a normal user without su and it did not work

    Here I did it as su and it worked although I got some error messages:
    Code:
    asty:/home/joe # winecfg
    wine: created the configuration directory '/root/.wine'
    fixme:storage:create_storagefile Storage share mode not implemented.
    err:mscoree:LoadLibraryShim error reading registry key for installroot
    err:mscoree:LoadLibraryShim error reading registry key for installroot
    err:mscoree:LoadLibraryShim error reading registry key for installroot
    err:mscoree:LoadLibraryShim error reading registry key for installroot
    fixme:storage:create_storagefile Storage share mode not implemented.
    fixme:iphlpapi:NotifyAddrChange (Handle 0xdde368, overlapped 0xdde380): stub
    fixme:storage:create_storagefile Storage share mode not implemented.
    fixme:iphlpapi:NotifyAddrChange (Handle 0x10ee8b0, overlapped 0x10ee8bc): stub
    wine: configuration in '/root/.wine' has been updated.
    Greetings, Joe

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •