landscape-sysinfo crashed with IOError in __init__()

Hello Thomas,

do you remember when the backtrace happened? Did you login on a terminal or via ssh for instance?

Could you also please show the output of these commands:

ls -lad /home/thomas /home/thomas/.landscape
ls -la /home/thomas/.landscape

The backtrace shows that landscape-sysinfo tried to write somewhere in /home/username (sic), instead of /home/thomas, so that looks wierd.

Do you have, or did you have at some point, a user account whose login name was "username"?

Do you have another entry in /etc/passwd with the uid of 1000?

thomas@thomas-laptop:~$ ls -lad /home/thomas /home/thomas/.landscape
ls: cannot access /home/thomas/.landscape: No such file or directory
drwxr-xr-x 61 thomas thomas 4096 2008-09-26 21:53 /home/thomas
thomas@thomas-laptop:~$ ls -la /home/thomas/.landscape
ls: cannot access /home/thomas/.landscape: No such file or directory
thomas@thomas-laptop:~$ ls -lad /home/thomas
drwxr-xr-x 61 thomas thomas 4096 2008-09-26 21:53 /home/thomas
thomas@thomas-laptop:~$ lsb_release -rd ; uname -a ; apt-cache policy linux landscape dpkg-reconfigure dpkg
Description: Ubuntu intrepid (development branch)
Release: 8.10
Linux thomas-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC 2008 i686 GNU/Linux
linux:
  Installed: 2.6.27.4.4
  Candidate: 2.6.27.4.4
  Version table:
 *** 2.6.27.4.4 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
     2.6.27.3.3 0
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Alpha i386 (20080917.1) intrepid/restricted Packages
dpkg:
  Installed: 1.14.20ubuntu6
  Candidate: 1.14.20ubuntu6
  Version table:
 *** 1.14.20ubuntu6 0
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Alpha i386 (20080917.1) intrepid/main Packages
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
W: Unable to locate package landscape
W: Unable to locate package dpkg-reconfigure
thomas@thomas-laptop:~$ sudo apt-get source landscape dpkg-reconfigure
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to find a source package for landscape
thomas@thomas-laptop:~$ sudo apt-get source landscape-client dpkg-reconfigure
Reading package lists... Done
Building dependency tree
Reading state information... Done
NOTICE: 'landscape-client' packaging is maintained in the 'Bzr' version control system at:
http://bazaar.launchpad.net/~ubuntu-core-dev/landscape-client/ubuntu/files
Please use:
bzr get http://bazaar.launchpad.net/~ubuntu-core-dev/landscape-client/ubuntu/files
to retrieve the latest (possible unreleased) updates to the package.
E: Unable to find a source package for dpkg-reconfigure
thomas@thomas-laptop:~$ bzr landscape-client
bzr: ERROR: unknown command "landscape-client"
thomas@thomas-laptop:~$
thomas@thomas-laptop:~$ bzr get http://bazaar.launchpad.net/~ubuntu-core-dev/landscape-client/ubuntu/files
bzr: ERROR: Invalid http response for http://bazaar.launchpad.net/%7Eubuntu-core-dev/landscape-client/ubuntu/files/.bzr/branch-format: Unable to handle http code 500: Internal Server Error
thomas@thomas-laptop:~$ lsb_release -rd ; uname -a ; apt-cache policy linux landscape-client dpkg
Description: Ubuntu intrepid (development branch)
Release: 8.10
Linux thomas-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC 2008 i686 GNU/Linux
linux:
  Installed: 2.6.27.4.4
  Candidate: 2.6.27.4.4
  Version table:
 *** 2.6.27.4.4 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
     2.6.27.3.3 0
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Alpha i386 (20080917.1) intrepid/restricted Packages
landscape-client:
  Installed: (none)
  Candidate: 1.0.21.1-0u...

System info:

Acer Aspire 9410-4933
Intel Core Duo processor T2450
(2.0 GHz, 533 MHz FSB, 2MB L2 cache)
17" WXGA+ Acer CrystalBrite LCD
Intel Graphics Media Accelerator 950
160GB HDD
DVD-Super Multi double layer
(support DVD+-R Double Layer/DVD+-RW)
1GB DDR2
802.11a/b/g wireless LAN

Hello Thomas,

thanks for the information. But I think you missed some of my questions:

Do you have, or did you have at some point, a user account whose login name was "username"?

Do you have another entry in /etc/passwd with the uid of 1000?

I ask these because the apport log that was attached contained these:
* IOError: [Errno 13] Permission denied: '/home/username/.landscape/sysinfo.log'
* Uid: 1000 1000 1000 1000
* Gid: 1000 1000 1000 1000

I don't know if "username" was for real or if apport is mangling the data and replacing the real username. It also shows that the uid/gid pair is 1000, which is typically the first user created in ubuntu. And the "permission denied" error is very specific. So, I don't know which username crashed landscape.

Your mail to 'launchpad-users' with the subject

    feedback

Is being held until the list moderator can review it for approval.

The reason it is being held:

    Post to moderated list

Either the message will get posted to the list, or you will receive
notification of the moderator's decision. If you would like to cancel
this posting, please visit the following URL:

    https://lists.ubuntu.com/mailman/confirm/launchpad-users/f104883df70e01b653d6db90a22d81685b686ecd

Bad confirmation string
Invalid confirmation string: f104883df70e01b653d6db90a22d81685b686ecd.

Note that confirmation strings expire approximately 3 days after the initial subscription request. If your confirmation has expired, please try to re-submit your subscription. Otherwise, re-enter your confirmation string.
launchpad-users list run by kiko at async.com.br, matthew.revell at canonical.com, joey at canonical.com
launchpad-users administrative interface (requires authorization)
Overview of all lists.canonical.com mailing lists

Delivered by Mailman
version 2.1.8 Python Powered Gnu's Not Unix

Hi there,

I am going to stop reporting bug reports for now, as you people will not read them anyway.

I have confirmed with the help of canonical support that the laptop I am using has no defective hardware. The BIOS is not broke, since I have reflashed the BIOS with an upgraded version, from the Acer website. For the few bugs I could easily reproduce this does not change a thing. What we have found out is that the BIOS developed by the Phoenix people for Acer, does not support 4 GB. Acer claims that the system supports 4 GB, but the people from Phoenix must have limited the BIOS to 3 GB, since it was made for use with Windows 32-bit. The system has two identical sodim sockets and I have two identical 2 GB chips, that were sold to me fully installed by an official eBay reseller. I have tested both sockets and both chips by memtest86+ 1.65 1.70 and 2.01. Everything came up clean except the alfa 5 2.01 test, which had a bug, but is now fixed. I had a problem before when trying to upgrade to Vista Ultimate, as the 32-bit only recognises 3 GB. Back then a faulty memtest86+ test surfaced. I have the memtest86+ version in backup, but it is preinstalled and backed up with Windows Live OneCare and I have no idea how to determine the version number. Really it does not change anything, as when I remove one of the chips, the same bugs seem to persist. That is, the ones that are easily reproducible. I now get less crashes both due to the fact that I now only run Ubuntu repositories, other than VirtualBox 2.0.2 and Skype-debian as described in the community docs, as well as alfa 6 and maybe also because I only use 2 GB and the BIOS update. I do use many multiverse and restricted applications though.

I maybe still able to help with the following data:

My AptonCD bug persists. Only faster since I now use only 2 GB RAM. I have tracked and described this behaviour with gnome-system-monitor and Valgrind log several weeks ago, but Tormod would not look into it since he suspected hardware failure. The problem is there that APTonCD writes everything away to the RAM chip(s) and crashes when...

--Output from 'thomas@thomas-laptop:~$ gedit /etc/passwd'--

root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/bin/sh
bin:x:2:2:bin:/bin:/bin/sh
sys:x:3:3:sys:/dev:/bin/sh
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/bin/sh
man:x:6:12:man:/var/cache/man:/bin/sh
lp:x:7:7:lp:/var/spool/lpd:/bin/sh
mail:x:8:8:mail:/var/mail:/bin/sh
news:x:9:9:news:/var/spool/news:/bin/sh
uucp:x:10:10:uucp:/var/spool/uucp:/bin/sh
proxy:x:13:13:proxy:/bin:/bin/sh
www-data:x:33:33:www-data:/var/www:/bin/sh
backup:x:34:34:backup:/var/backups:/bin/sh
list:x:38:38:Mailing List Manager:/var/list:/bin/sh
irc:x:39:39:ircd:/var/run/ircd:/bin/sh
gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/bin/sh
nobody:x:65534:65534:nobody:/nonexistent:/bin/sh
libuuid:x:100:101::/var/lib/libuuid:/bin/sh
syslog:x:101:103::/home/syslog:/bin/false
klog:x:102:104::/home/klog:/bin/false
avahi-autoipd:x:103:112:Avahi autoip daemon,,,:/var/lib/avahi-autoipd:/bin/false
pulse:x:104:114:PulseAudio daemon,,,:/var/run/pulse:/bin/false
saned:x:105:117::/home/saned:/bin/false
messagebus:x:106:118::/var/run/dbus:/bin/false
polkituser:x:107:119:PolicyKit,,,:/var/run/PolicyKit:/bin/false
avahi:x:108:120:Avahi mDNS daemon,,,:/var/run/avahi-daemon:/bin/false
haldaemon:x:109:121:Hardware abstraction layer,,,:/var/run/hald:/bin/false
hplip:x:110:7:HPLIP system user,,,:/var/run/hplip:/bin/false
gdm:x:111:123:Gnome Display Manager:/var/lib/gdm:/bin/false
thomas:x:1000:1000:Thomas Delbeke,,,:/home/thomas:/bin/bash
landscape:x:112:65534:Landscape Client Daemon,,,:/var/lib/landscape:/bin/false
clamav:x:113:126::/var/lib/clamav:/bin/false
beagleindex:x:114:65534::/var/cache/beagle:/bin/false
backuppc:x:115:128:BackupPC,,,:/var/lib/backuppc:/bin/sh
Debian-exim:x:116:129::/var/spool/exim4:/bin/false
uml-net:x:117:130::/home/uml-net:/bin/false

thomas@thomas-laptop:/usr/src$ cd
thomas@thomas-laptop:~$ cd /etc/passwd
bash: cd: /etc/passwd: Not a directory
thomas@thomas-laptop:~$ gedit /etc/passwd
thomas@thomas-laptop:~$ sudo dpkg-reconfigure landscape-client
[sudo] password for thomas:
landscape-client is not configured, please run landscape-config.
 * Reloading system message bus config... [ OK ]
landscape-client is not configured, please run landscape-config.
thomas@thomas-laptop:~$ sudo landscape-config

The Landscape client must be started on boot to operate correctly.

Start Landscape client on boot? (Y/n): y

This script will interactively set up the Landscape client. It will
ask you a few questions about this computer and your Landscape
account, and will submit that information to the Landscape server.
After this computer is registered it will need to be approved by an
account administrator on the pending computers page.

Please see https://landscape.canonical.com for more information.

The computer title you provide will be used to represent this
computer in the Landscape user interface. It's important to use
a title that will allow the system to be easily recognized when
it appears on the pending computers page.

This computer's title: thomas

You must now specify the name of the Landscape account you
want to register this computer with. You can verify the
names of the accounts you manage on your dashboard at
https://landscape.canonical.com/dashboard

Account name: thomas delbeke

A registration password may be associated with your Landscape
account to prevent unauthorized registration attempts. This
is not your personal login password. It is optional, and unless
explicitly set on the server, it may be skipped here.

If you don't remember the registration password you can find it
at https://landscape.canonical.com/account/thomas delbeke

Account registration password:
Please confirm:

The Landscape client communicates with the server over HTTP and
HTTPS. If your network requires you to use a proxy to access HTTP
and/or HTTPS web sites, please provide the address of these
proxies now. If you don't use a proxy, leave these fields empty.

HTTP proxy URL:
HTTPS proxy URL:

Landscape has a feature which enables administrators to run
arbitrary scripts on machines under their control. By default this
feature is disabled in the client, disallowing any arbitrary script
execution. If enabled, the set of users that scripts may run as is
also configurable.

Enable script execution? [y/N]y

By default, scripts are restricted to the 'landscape' and
'nobody' users. Please enter a comma-delimited list of users
that scripts will be restricted to. To allow scripts to be run
by any user, enter "ALL".

Script users: all
 * Stopping landscape-client daemon [fail]
 * Starting the landscape-client daemon [ OK ]

Request a new registration for this computer now? (Y/n): n
thomas@thomas-laptop:~$

thomas@thomas-laptop:~$ cd /var
thomas@thomas-laptop:/var$ ls
backups crash lib lock mail run tmp
cache games local log opt spool www
thomas@thomas-laptop:/var$ cd crash
thomas@thomas-laptop:/var/crash$ ls
_sbin_telinit.0.crash
_usr_bin_compiz.real.1000.crash
_usr_bin_deluge.1000.crash
_usr_bin_software-properties-gtk.0.crash
_usr_bin_update-manager.0.crash
_usr_lib_firefox-3.0.3_firefox.1000.crash
_usr_lib_gvfs_gvfsd-trash.1000.crash
_usr_sbin_console-kit-daemon.0.crash
_usr_sbin_NetworkManager.0.crash
thomas@thomas-laptop:/var/crash$

thomas@thomas-laptop:/var/crash$ cd
thomas@thomas-laptop:~$ sudo dpkg-reconfigure landscape-client
 * Stopping landscape-client daemon [ OK ]
 * Reloading system message bus config... [ OK ]
 * Starting the landscape-client daemon [ OK ]
thomas@thomas-laptop:~$ sudo landscape-config

This script will interactively set up the Landscape client. It will
ask you a few questions about this computer and your Landscape
account, and will submit that information to the Landscape server.
After this computer is registered it will need to be approved by an
account administrator on the pending computers page.

Please see https://landscape.canonical.com for more information.

The computer title you provide will be used to represent this
computer in the Landscape user interface. It's important to use
a title that will allow the system to be easily recognized when
it appears on the pending computers page.

This computer's title [thomas]:

You must now specify the name of the Landscape account you
want to register this computer with. You can verify the
names of the accounts you manage on your dashboard at
https://landscape.canonical.com/dashboard

Account name [thomas delbeke]:

A registration password may be associated with your Landscape
account to prevent unauthorized registration attempts. This
is not your personal login password. It is optional, and unless
explicitly set on the server, it may be skipped here.

If you don't remember the registration password you can find it
at https://landscape.canonical.com/account/thomas delbeke

Account registration password:

The Landscape client communicates with the server over HTTP and
HTTPS. If your network requires you to use a proxy to access HTTP
and/or HTTPS web sites, please provide the address of these
proxies now. If you don't use a proxy, leave these fields empty.

HTTP proxy URL:
HTTPS proxy URL:

Landscape has a feature which enables administrators to run
arbitrary scripts on machines under their control. By default this
feature is disabled in the client, disallowing any arbitrary script
execution. If enabled, the set of users that scripts may run as is
also configurable.

Enable script execution? [Y/n]y

By default, scripts are restricted to the 'landscape' and
'nobody' users. Please enter a comma-delimited list of users
that scripts will be restricted to. To allow scripts to be run
by any user, enter "ALL".

Script users [all]:
 * Stopping landscape-client daemon [ OK ]
 * Starting the landscape-client daemon [ OK ]

Request a new registration for this computer now? (Y/n): y
Please wait... Invalid account name or registration password.
thomas@thomas-laptop:~$ sudo dpkg-reconfigure landscape-client
 * Stopping landscape-client daemon [ OK ]
 * Reloading system message bus config... [ OK ]
 * Starting the landscape-client daemon [ OK ]
thomas@thomas-laptop:~$ sudo landscape-config

This script will interactively set u...

thomas@thomas-laptop:~$ cd /var
thomas@thomas-laptop:/var$ ls
backups crash lib lock mail run tmp
cache games local log opt spool www
thomas@thomas-laptop:/var$ cd crash
thomas@thomas-laptop:/var/crash$ ls
_sbin_telinit.0.crash
_usr_bin_compiz.real.1000.crash
_usr_bin_deluge.1000.crash
_usr_bin_software-properties-gtk.0.crash
_usr_bin_update-manager.0.crash
_usr_lib_firefox-3.0.3_firefox.1000.crash
_usr_lib_gvfs_gvfsd-trash.1000.crash
_usr_sbin_console-kit-daemon.0.crash
_usr_sbin_NetworkManager.0.crash
thomas@thomas-laptop:/var/crash$ ls -la
total 19016
drwxrwxrwt 2 root root 4096 2008-09-30 06:59 .
drwxr-xr-x 16 root root 4096 2008-09-28 12:00 ..
-rw------- 1 root root 28085 2008-09-29 16:56 _sbin_telinit.0.crash
-rw------- 1 thomas thomas 345139 2008-09-28 16:38 _usr_bin_compiz.real.1000.crash
---------- 1 thomas thomas 1426237 2008-09-28 07:45 _usr_bin_deluge.1000.crash
-rw------- 1 root root 37526 2008-09-28 10:20 _usr_bin_software-properties-gtk.0.crash
-rw------- 1 root root 10536472 2008-09-28 12:03 _usr_bin_update-manager.0.crash
---------- 1 thomas thomas 4252806 2008-09-29 17:21 _usr_lib_firefox-3.0.3_firefox.1000.crash
-rw------- 1 thomas thomas 117781 2008-09-27 22:52 _usr_lib_gvfs_gvfsd-trash.1000.crash
-rw------- 1 root root 231515 2008-09-29 22:16 _usr_sbin_console-kit-daemon.0.crash
-rw------- 1 root root 2420554 2008-09-29 18:27 _usr_sbin_NetworkManager.0.crash
thomas@thomas-laptop:/var/crash$

thomas@thomas-laptop:~$ lsb_release -rd ; uname -a ; apt-cache policy linux linux-source-2.6.27 linux-headers-generic linux-image-generic apport-gtk landscape-client landscape-sysinfo landscape-config landscape
Description: Ubuntu intrepid (development branch)
Release: 8.10
Linux thomas-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC 2008 i686 GNU/Linux
linux:
  Installed: 2.6.27.4.4
  Candidate: 2.6.27.4.4
  Version table:
 *** 2.6.27.4.4 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
linux-source-2.6.27:
  Installed: 2.6.27-4.6
  Candidate: 2.6.27-4.6
  Version table:
 *** 2.6.27-4.6 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-headers-generic:
  Installed: 2.6.27.4.4
  Candidate: 2.6.27.4.4
  Version table:
 *** 2.6.27.4.4 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-image-generic:
  Installed: 2.6.27.4.4
  Candidate: 2.6.27.4.4
  Version table:
 *** 2.6.27.4.4 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
apport-gtk:
  Installed: 0.116
  Candidate: 0.116
  Version table:
 *** 0.116 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
landscape-client:
  Installed: 1.0.21.1-0ubuntu1
  Candidate: 1.0.21.1-0ubuntu1
  Version table:
 *** 1.0.21.1-0ubuntu1 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
W: Unable to locate package landscape-sysinfo
W: Unable to locate package landscape-config
W: Unable to locate package landscape
thomas@thomas-laptop:~$

thomas@thomas-laptop:~$ lsb_release -rd ; uname -a ; apt-cache policy linux linux-source-2.6.27 linux-headers-generic linux-image-generic apport-gtk landscape-client landscape-common dpkg
Description: Ubuntu intrepid (development branch)
Release: 8.10
Linux thomas-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC 2008 i686 GNU/Linux
linux:
  Installed: 2.6.27.4.4
  Candidate: 2.6.27.4.4
  Version table:
 *** 2.6.27.4.4 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
linux-source-2.6.27:
  Installed: 2.6.27-4.6
  Candidate: 2.6.27-4.6
  Version table:
 *** 2.6.27-4.6 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-headers-generic:
  Installed: 2.6.27.4.4
  Candidate: 2.6.27.4.4
  Version table:
 *** 2.6.27.4.4 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-image-generic:
  Installed: 2.6.27.4.4
  Candidate: 2.6.27.4.4
  Version table:
 *** 2.6.27.4.4 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
apport-gtk:
  Installed: 0.116
  Candidate: 0.116
  Version table:
 *** 0.116 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
landscape-client:
  Installed: 1.0.21.1-0ubuntu1
  Candidate: 1.0.21.1-0ubuntu1
  Version table:
 *** 1.0.21.1-0ubuntu1 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
landscape-common:
  Installed: 1.0.21.1-0ubuntu1
  Candidate: 1.0.21.1-0ubuntu1
  Version table:
 *** 1.0.21.1-0ubuntu1 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
dpkg:
  Installed: 1.14.20ubuntu6
  Candidate: 1.14.20ubuntu6
  Version table:
 *** 1.14.20ubuntu6 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
thomas@thomas-laptop:~$

thomas@thomas-laptop:~$ sudo dpkg-reconfigure landscape-client | sudo landscape-config

This script will interactively set up the Landscape client. It will
ask you a few questions about this computer and your Landscape
account, and will submit that information to the Landscape server.
After this computer is registered it will need to be approved by an
account administrator on the pending computers page.

Please see https://landscape.canonical.com for more information.

The computer title you provide will be used to represent this
computer in the Landscape user interface. It's important to use
a title that will allow the system to be easily recognized when
it appears on the pending computers page.

This computer's title [thomas]:
You must now specify the name of the Landscape account you
want to register this computer with. You can verify the
names of the accounts you manage on your dashboard at
https://landscape.canonical.com/dashboard

Account name [thomas delbeke]:
A registration password may be associated with your Landscape
account to prevent unauthorized registration attempts. This
is not your personal login password. It is optional, and unless
explicitly set on the server, it may be skipped here.

If you don't remember the registration password you can find it
at https://landscape.canonical.com/account/ ...done.

(22, 'Invalid argument')
Aborting Landscape configuration
 * Reloading system message bus config... [ OK ]
                                                                                * Starting the landscape-client daemon [ OK ]
                                                                               thomas@thomas-laptop:~$

Hi there,

I could not reproduce this crash so far, but I managed to crash gnome-terminal with a nonsense pipe.

(thomas@thomas-laptop:~$ sudo dpkg-reconfigure landscape-client | sudo landscape-config)

You fancy a gdb backtrace from this?

Cheers,

Thomas

Hi Thomas,

thanks for the info.

That landscape-client/landscape-config crash will happen again if you run it as a regular user instead of root, or without using sudo. That's somewhat expected and we will fix it so it doesn't crash, but prints a nice error message. That is being tracked in bug #268879.

landscape-sysinfo, however, is something else. It can run both as root or as a regular user. When run as a regular user, it parses a config file in the user's home directory (inside ~/.landscape/ actually), and that's where it also logs its output. The crash you reported happened while trying to log something there: it got a permission denied error. That's odd, because it would mean that the user cannot write to his/her own home directory. I can only see this happening if it was run via sudo to another user, like this:

$ sudo -u anotheruser landscape-sysinfo

If user "foo" ran the above, we would see a crash, because landscape-sysinfo would be running as "anotheruser" but with "foo"'s environment, in particular his HOME var. This, however, would work:

$ sudo -u anotheruser -H landscape-sysinfo

landscape-sysinfo is designed to print a summary of the system information upon a terminal/ssh login. It can run every time such a login happens, or every 10min via a cron job that will cache that information. You can configure this behaviour via "dpkg --reconfigure landscape-common" and "update-motd --enable".

So, if you want to keep trying to reproduce the crash, please use "landscape-sysinfo" in your tests, which is what crashed according to the original apport report.

Thanks!

Hi Andreas,

please check this out (Bug #277208):

thomas@thomas-laptop:~$ landscape-client
Traceback (most recent call last):
  File "/usr/bin/landscape-client", line 13, in <module>
    sys.exit(run())
  File "/usr/lib/python2.5/site-packages/landscape/watchdog.py", line 500, in run
    init_logging(config, "watchdog")
  File "/usr/lib/python2.5/site-packages/landscape/deployment.py", line 32, in init_logging
    handlers.append(FileHandler(log_filename))
  File "/usr/lib/python2.5/logging/__init__.py", line 770, in __init__
    stream = open(filename, mode)
IOError: [Errno 13] Permission denied: '/var/log/landscape/watchdog.log'
thomas@thomas-laptop:~$

But now:

thomas@thomas-laptop:~$ cd /var/log/landscape/watchdog.log
bash: cd: /var/log/landscape/watchdog.log: No such file or directory
thomas@thomas-laptop:~$ cd /var/log/landscape/
thomas@thomas-laptop:/var/log/landscape$ ls
sysinfo.log
thomas@thomas-laptop:/var/log/landscape$ gedit ./sys*
thomas@thomas-laptop:/var/log/landscape$ ls -la
total 8
drwxr-xr-x 2 landscape root 4096 2008-10-03 02:43 .
drwxr-xr-x 20 root root 4096 2008-10-14 01:27 ..
-rw-r--r-- 1 landscape root 0 2008-10-03 02:43 sysinfo.log
thomas@thomas-laptop:/var/log/landscape$ sudo apt-get source

thomas@thomas-laptop:~$ cd /var/log/landscape/watchdog.log
bash: cd: /var/log/landscape/watchdog.log: No such file or directory
thomas@thomas-laptop:~$ cd /var/log/landscape/
thomas@thomas-laptop:/var/log/landscape$ ls
sysinfo.log
thomas@thomas-laptop:/var/log/landscape$ gedit ./sys*
thomas@thomas-laptop:/var/log/landscape$ ls -la
total 8
drwxr-xr-x 2 landscape root 4096 2008-10-03 02:43 .
drwxr-xr-x 20 root root 4096 2008-10-14 01:27 ..
-rw-r--r-- 1 landscape root 0 2008-10-03 02:43 sysinfo.log
thomas@thomas-laptop:/var/log/landscape$ sudo apt-get source watchdog
[sudo] password for thomas:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Need to get 179kB of source archives.
Get: 1 http://gb.archive.ubuntu.com intrepid/universe watchdog 5.4-5 (dsc) [579B]
Get: 2 http://gb.archive.ubuntu.com intrepid/universe watchdog 5.4-5 (tar) [176kB]
Get: 3 http://gb.archive.ubuntu.com intrepid/universe watchdog 5.4-5 (diff) [2138B]
Fetched 179kB in 8s (22.2kB/s)
gpg: WARNING: unsafe ownership on configuration file `/home/thomas/.gnupg/gpg.conf'
gpg: Signature made Sat 29 Dec 2007 12:37:26 GMT using DSA key ID 29F19BD1
gpg: Can't check signature: public key not found
dpkg-source: extracting watchdog in watchdog-5.4
dpkg-source: info: unpacking watchdog_5.4.orig.tar.gz
dpkg-source: info: applying watchdog_5.4-5.diff.gz
thomas@thomas-laptop:/var/log/landscape$ cd /var/log/landscape/watchdog.log
bash: cd: /var/log/landscape/watchdog.log: No such file or directory
thomas@thomas-laptop:/var/log/landscape$ sudo dpkg-reconfigure dash
thomas@thomas-laptop:/var/log/landscape$ cd /var/log/landscape/watchdog.log
bash: cd: /var/log/landscape/watchdog.log: No such file or directory
thomas@thomas-laptop:/var/log/landscape$ sudo dpkg-reconfigure dash
Removing `diversion of /bin/sh to /bin/sh.distrib by dash'
Removing `diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash'
thomas@thomas-laptop:/var/log/landscape$ cd /var/log/landscape/watchdog.log
bash: cd: /var/log/landscape/watchdog.log: No such file or directory
thomas@thomas-laptop:/var/log/landscape$ sudo apt-get install watchdog
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed
  watchdog
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 69.4kB of archives.
After this operation, 291kB of additional disk space will be used.
Get: 1 http://gb.archive.ubuntu.com intrepid/universe watchdog 5.4-5 [69.4kB]
Fetched 69.4kB in 3s (18.0kB/s)
Preconfiguring packages ...
Selecting previously deselected package watchdog.
(Reading database ... 194184 files and directories currently installed.)
Unpacking watchdog (from .../watchdog_5.4-5_i386.deb) ...
Processing triggers for man-db ...
Setting up watchdog (5.4-5) ...
udev active, devices will be created in /dev/.static/dev/
rm: cannot remove `logibm-': Read-only file system
mknod: `logibm-': Read-only file system
makedev logibm c 10 0 root root 0660: failed
rm: cannot remove `logibm-': Read-only file system
rm: cannot re...

drwxr-xr-x 3 landscape root 4096 2008-10-14 05:04 .
drwxr-xr-x 21 root root 4096 2008-10-14 05:07 ..
-rw-r--r-- 1 landscape root 0 2008-10-03 02:43 sysinfo.log
drwxr-xr-x 6 root root 4096 2007-08-17 11:51 watchdog-5.4
-rw-r--r-- 1 root root 2138 2008-05-03 05:12 watchdog_5.4-5.diff.gz
-rw-r--r-- 1 root root 579 2008-05-03 05:12 watchdog_5.4-5.dsc
-rw-r--r-- 1 root root 176060 2007-10-24 11:05 watchdog_5.4.orig.tar.gz
thomas@thomas-laptop:/var/log/landscape$ landscape-sysinfo
The program 'landscape-sysinfo' is currently not installed. You can install it by typing:
sudo apt-get install landscape-common
bash: landscape-sysinfo: command not found
thomas@thomas-laptop:/var/log/landscape$ sudo apt-get install landscape-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  update-motd
The following NEW packages will be installed
  landscape-common update-motd
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 153kB of archives.
After this operation, 1020kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get: 1 http://gb.archive.ubuntu.com intrepid/main update-motd 1.8 [6782B]
Get: 2 http://gb.archive.ubuntu.com intrepid/main landscape-common 1.0.21.1-0ubuntu2 [147kB]
Fetched 153kB in 8s (19.0kB/s)
Preconfiguring packages ...
Selecting previously deselected package update-motd.
(Reading database ... 194209 files and directories currently installed.)
Unpacking update-motd (from .../update-motd_1.8_all.deb) ...
Selecting previously deselected package landscape-common.
Unpacking landscape-common (from .../landscape-common_1.0.21.1-0ubuntu2_all.deb) ...
Processing triggers for man-db ...
Setting up update-motd (1.8) ...

Setting up landscape-common (1.0.21.1-0ubuntu2) ...

thomas@thomas-laptop:/var/log/landscape$ sudo apt-get install landscape-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  python-pexpect python-pycurl python-smartpm
Suggested packages:
  libcurl4-gnutls-dev python-pycurl-dbg
The following NEW packages will be installed
  landscape-client python-pexpect python-pycurl python-smartpm
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 300kB/418kB of archives.
After this operation, 3289kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get: 1 http://gb.archive.ubuntu.com intrepid/main python-pycurl 7.18.2-1build1 [79.9kB]
Get: 2 http://gb.archive.ubuntu.com intrepid/main python-smartpm 1.1.1~bzr20081010-0ubuntu0.8.10 [202kB]
Get: 3 http://gb.archive.ubuntu.com intrepid/main landscape-client 1.0.21.1-0ubuntu2 [17.8kB]
Fetched 300kB in 9s (31.8kB/s)
Preconfiguring packages ...
Selecting previously deselected package python-pycurl.
(Reading database ... 194333 files and directories currently installed.)
Unpacking python-pycurl (from .../python-pycurl_7.18.2-1build1_i386.deb) ...
Selecting previously deselec...

thomas@thomas-laptop:/var/log/landscape$ ls -la
total 196
drwxr-xr-x 3 landscape root 4096 2008-10-14 05:04 .
drwxr-xr-x 21 root root 4096 2008-10-14 05:07 ..
-rw-r--r-- 1 landscape root 0 2008-10-03 02:43 sysinfo.log
drwxr-xr-x 6 landscape root 4096 2007-08-17 11:51 watchdog-5.4
-rw-r--r-- 1 landscape root 2138 2008-05-03 05:12 watchdog_5.4-5.diff.gz
-rw-r--r-- 1 landscape root 579 2008-05-03 05:12 watchdog_5.4-5.dsc
-rw-r--r-- 1 landscape root 176060 2007-10-24 11:05 watchdog_5.4.orig.tar.gz
thomas@thomas-laptop:/var/log/landscape$ update-motd --enable
update-motd is now enabled.
/usr/sbin/update-motd: line 103: /var/run/motd.new: Permission denied
thomas@thomas-laptop:/var/log/landscape$ update-motd --enable

thomas@thomas-laptop:/var/log/landscape$ update-motd --enable
update-motd is now enabled.
/usr/sbin/update-motd: line 103: /var/run/motd.new: Permission denied
thomas@thomas-laptop:/var/log/landscape$ sudo update-motd --enable
update-motd is now enabled.
thomas@thomas-laptop:/var/log/landscape$ update-motd --enable
update-motd is now enabled.
/usr/sbin/update-motd: line 103: /var/run/motd.new: Permission denied
thomas@thomas-laptop:/var/log/landscape$ landscape-config --url <email address hidden>

The Landscape client must be started on boot to operate correctly.

Start Landscape client on boot? (Y/n): y
[Errno 13] Permission denied: '/etc/default/landscape-client'
Aborting Landscape configuration
thomas@thomas-laptop:/var/log/landscape$ pwd
/var/log/landscape
thomas@thomas-laptop:/var/log/landscape$ ls -la
total 196
drwxr-xr-x 3 landscape root 4096 2008-10-14 05:04 .
drwxr-xr-x 21 root root 4096 2008-10-14 05:07 ..
-rw-r--r-- 1 landscape root 0 2008-10-03 02:43 sysinfo.log
drwxr-xr-x 6 landscape root 4096 2007-08-17 11:51 watchdog-5.4
-rw-r--r-- 1 landscape root 2138 2008-05-03 05:12 watchdog_5.4-5.diff.gz
-rw-r--r-- 1 landscape root 579 2008-05-03 05:12 watchdog_5.4-5.dsc
-rw-r--r-- 1 landscape root 176060 2007-10-24 11:05 watchdog_5.4.orig.tar.gz
thomas@thomas-laptop:/var/log/landscape$ landscape-sysinfo
  System load: 0.36 Swap usage: 0% Users logged in: 1
  Usage of /: 77.0% of 145.89GB Temperature: 63 C
  Memory usage: 33% Processes: 137

  => There is 1 zombie process.

  Graph these measurements at https://landscape.canonical.com
thomas@thomas-laptop:/var/log/landscape$

thomas@thomas-laptop:/var/log/landscape$ landscape-sysinfo
  System load: 0.36 Swap usage: 0% Users logged in: 1
  Usage of /: 77.0% of 145.89GB Temperature: 63 C
  Memory usage: 33% Processes: 137

  => There is 1 zombie process.

  Graph these measurements at https://landscape.canonical.com
thomas@thomas-laptop:/var/log/landscape$ ls -la
total 196
drwxr-xr-x 3 landscape root 4096 2008-10-14 05:04 .
drwxr-xr-x 21 root root 4096 2008-10-14 05:07 ..
-rw-r--r-- 1 landscape root 0 2008-10-03 02:43 sysinfo.log
drwxr-xr-x 6 landscape root 4096 2007-08-17 11:51 watchdog-5.4
-rw-r--r-- 1 landscape root 2138 2008-05-03 05:12 watchdog_5.4-5.diff.gz
-rw-r--r-- 1 landscape root 579 2008-05-03 05:12 watchdog_5.4-5.dsc
-rw-r--r-- 1 landscape root 176060 2007-10-24 11:05 watchdog_5.4.orig.tar.gz
thomas@thomas-laptop:/var/log/landscape$ sudo landscape-sysinfo
  System load: 0.3 Swap usage: 0% Users logged in: 1
  Usage of /: 77.0% of 145.89GB Temperature: 64 C
  Memory usage: 33% Processes: 136

  Graph these measurements at https://landscape.canonical.com
thomas@thomas-laptop:/var/log/landscape$ landscape-sysinfo
  System load: 0.23 Swap usage: 0% Users logged in: 1
  Usage of /: 77.0% of 145.89GB Temperature: 63 C
  Memory usage: 33% Processes: 136

  Graph these measurements at https://landscape.canonical.com
thomas@thomas-laptop:/var/log/landscape$ landscape-config
error: must specify --url or the 'url' directive in the config file.
thomas@thomas-laptop:/var/log/landscape$ landscape-config --url <email address hidden>

The Landscape client must be started on boot to operate correctly.

Start Landscape client on boot? (Y/n): y
[Errno 13] Permission denied: '/etc/default/landscape-client'
Aborting Landscape configuration
thomas@thomas-laptop:/var/log/landscape$ sudo landscape-config --url <email address hidden>

The Landscape client must be started on boot to operate correctly.

Start Landscape client on boot? (Y/n): y

This script will interactively set up the Landscape client. It will
ask you a few questions about this computer and your Landscape
account, and will submit that information to the Landscape server.
After this computer is registered it will need to be approved by an
account administrator on the pending computers page.

Please see https://landscape.canonical.com for more information.

The computer title you provide will be used to represent this
computer in the Landscape user interface. It's important to use
a title that will allow the system to be easily recognized when
it appears on the pending computers page.

This computer's title: y

You must now specify the name of the Landscape account you
want to register this computer with. You can verify the
names of the accounts you manage on your dashboard at
https://landscape.canonical.com/dashboard

Account name: y

A registration password may be associated with your Landscape
account to prevent unauthorized registration attempts. This
is not your personal login password. It is optional, and unless
explicitly set on the server, it may...

thomas@thomas-laptop:/var/log/landscape$ ls -la
total 212
drwxr-xr-x 3 landscape root 4096 2008-10-14 05:36 .
drwxr-xr-x 21 root root 4096 2008-10-14 05:07 ..
-rw------- 1 landscape nogroup 964 2008-10-14 05:37 broker.log
-rw------- 1 root root 1483 2008-10-14 05:36 manager.log
-rw------- 1 landscape nogroup 2571 2008-10-14 05:36 monitor.log
-rw-r--r-- 1 landscape root 0 2008-10-03 02:43 sysinfo.log
drwxr-xr-x 6 landscape root 4096 2007-08-17 11:51 watchdog-5.4
-rw-r--r-- 1 landscape root 2138 2008-05-03 05:12 watchdog_5.4-5.diff.gz
-rw-r--r-- 1 landscape root 579 2008-05-03 05:12 watchdog_5.4-5.dsc
-rw-r--r-- 1 landscape root 176060 2007-10-24 11:05 watchdog_5.4.orig.tar.gz
-rw-r--r-- 1 root root 93 2008-10-14 05:36 watchdog.log
thomas@thomas-laptop:/var/log/landscape$ sudo chmod -cR 777 ./*log ; sudo chown -cR 1000 ./*log
[sudo] password for thomas:
mode of `./broker.log' changed to 0777 (rwxrwxrwx)
mode of `./manager.log' changed to 0777 (rwxrwxrwx)
mode of `./monitor.log' changed to 0777 (rwxrwxrwx)
mode of `./sysinfo.log' changed to 0777 (rwxrwxrwx)
mode of `./watchdog.log' changed to 0777 (rwxrwxrwx)
changed ownership of `./broker.log' to 1000
changed ownership of `./manager.log' to 1000
changed ownership of `./monitor.log' to 1000
changed ownership of `./sysinfo.log' to 1000
changed ownership of `./watchdog.log' to 1000
thomas@thomas-laptop:/var/log/landscape$ sudo gedit /var/run/motd /etc/default/landscape-client ./broker.log ./manager.log ./monitor.log ./sysinfo.log ./watchdog.log
thomas@thomas-laptop:/var/log/landscape$

Thomas, I think you are misunderstanding the issue.

landscape-client WILL NOT run as a regular user. It has to be started as root. And that's what the initscript does (/etc/init.d/landscape-client). So, please, don't break your system trying to make landscape-client run as a regular user.

The same thing is valid for landscape-config: it WILL NOT run as a regular user.

The only program meant to be run by a regular user is landscape-sysinfo.

Hi Andreas,

I understood that already. I did fail to communicate properly with you though, for which my apologies. I had noticed earlier that I had a permission error for watchdog. I noticed that I did not have this installed in my current configuration. I cannot recall ever having installed watchdog myself. It also monitors your system, much like sysinfo. Therefore I suspected that this could have been the reason of the landscape-sysinfo crash. The watchdog program is standard in Debian kernels. I noticed the landscape/sysinfo.log was empty, although I ran landscape-sysinfo as well as sudo landscape-sysinfo many times over. I fear apport-gtk just does not detect it as a crash. It does not show up in /var/crash.

I have gathered the following log data and compiled them into an iso (see above logfiles.iso):

/var/run/motd
/etc/default/landscape-client
/var/log/landscape/broker.log
/var/log/landscape/manager.log
/var/log/landscape/monitor.log
/var/log/landscape/sysinfo.log
/var/log/landscape/watchdog.log

Can you verify if this is feasible?

Cheers,

Thomas

Thomas, I think at this point the best thing to do is to completely purge landscape-client and landscape-common from your system and reinstall it again.

this bug report has not received any activity for a long time, is this still an issue?

Hi
I'm not sure how I got subscribed to this bug report but it does not
appear relevant to me at all.
Sorry I can't be of any help to you.
Regards
John

On Fri, 2009-07-31 at 14:22 +0000, Dimitrios Symeonidis wrote:

> this bug report has not received any activity for a long time, is this
> still an issue?
>

_______
ubuntu

There were too many inconsistencies in this report and the system where it happened was changed too much in incorrect ways to reliably assess the report as a bug in landscape-sysinfo.

I'm closing this bug based on that. If it happens again on a pristine system with a fresh installation of landscape-common (of which landscape-sysinfo is part), then please reopen or just open a fresh new bug.

Thanks!