landscape-sysinfo crashed with IOError in __init__()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
landscape-client (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: landscape-client
thomas@
Description: Ubuntu intrepid (development branch)
Release: 8.10
Linux thomas-laptop 2.6.26-4-generic #1 SMP Mon Jul 14 18:39:53 UTC 2008 i686 GNU/Linux
landscape-client:
Installed: 1.0.18-0ubuntu1
Candidate: 1.0.18-0ubuntu1
Version table:
*** 1.0.18-0ubuntu1 0
500 http://
100 /var/lib/
linux:
Installed: (none)
Candidate: 2.6.27.3.3
Version table:
2.6.27.3.3 0
500 http://
dpkg:
Installed: 1.14.20ubuntu6
Candidate: 1.14.20ubuntu6
Version table:
*** 1.14.20ubuntu6 0
500 http://
100 /var/lib/
dpkg-dev:
Installed: 1.14.20ubuntu6
Candidate: 1.14.20ubuntu6
Version table:
*** 1.14.20ubuntu6 0
500 http://
100 /var/lib/
thomas@
ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/
InterpreterPath: /usr/bin/python2.5
Package: landscape-client 1.0.18-0ubuntu1
PackageArchitec
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=/
LANG=en_GB.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: landscape-client
Title: landscape-sysinfo crashed with IOError in __init__()
Uname: Linux 2.6.26-4-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
tdflanders (thomasdelbeke) wrote : | #1 |
- Dependencies.txt Edit (3.6 KiB, text/plain; charset="utf-8")
- ProcMaps.txt Edit (16.9 KiB, text/plain; charset="utf-8")
- ProcStatus.txt Edit (781 bytes, text/plain; charset="utf-8")
- Traceback.txt Edit (830 bytes, text/plain; charset="utf-8")
Andreas Hasenack (ahasenack) wrote : | #2 |
Changed in landscape-client: | |
status: | New → Incomplete |
tdflanders (thomasdelbeke) wrote : | #3 |
thomas@
ls: cannot access /home/thomas/
drwxr-xr-x 61 thomas thomas 4096 2008-09-26 21:53 /home/thomas
thomas@
ls: cannot access /home/thomas/
thomas@
drwxr-xr-x 61 thomas thomas 4096 2008-09-26 21:53 /home/thomas
thomas@
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://
100 /var/lib/
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://
100 /var/lib/
W: Unable to locate package landscape
W: Unable to locate package dpkg-reconfigure
thomas@
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to find a source package for landscape
thomas@
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://
Please use:
bzr get http://
to retrieve the latest (possible unreleased) updates to the package.
E: Unable to find a source package for dpkg-reconfigure
thomas@
bzr: ERROR: unknown command "landscape-client"
thomas@
thomas@
bzr: ERROR: Invalid http response for http://
thomas@
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://
100 /var/lib/
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...
tdflanders (thomasdelbeke) wrote : | #4 |
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
Andreas Hasenack (ahasenack) wrote : | #5 |
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/
* 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.
tdflanders (thomasdelbeke) wrote : | #6 |
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:/
Bad confirmation string
Invalid confirmation string: f104883df70e01b
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-
tdflanders (thomasdelbeke) wrote : | #7 |
--Output from 'thomas@
root:x:
daemon:
bin:x:2:
sys:x:3:
sync:x:
games:x:
man:x:6:
lp:x:7:7:lp:/var/spool/lpd:/bin/sh
mail:x:
news:x:
uucp:x:
proxy:x:
www-data:
backup:
list:x:
irc:x:39:
gnats:x:41:41:Gnats Bug-Reporting System (admin)
nobody:
libuuid:
syslog:
klog:x:
avahi-autoipd:
pulse:x:
saned:x:
messagebus:
polkituser:
avahi:x:
haldaemon:
hplip:x:110:7:HPLIP system user,,,
gdm:x:111:123:Gnome Display Manager:
thomas:
landscape:
clamav:
beagleindex:
backuppc:
Debian-
uml-net:
tdflanders (thomasdelbeke) wrote : | #8 |
thomas@
thomas@
bash: cd: /etc/passwd: Not a directory
thomas@
thomas@
[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@
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:/
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:/
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:/
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@
tdflanders (thomasdelbeke) wrote : | #9 |
thomas@
thomas@
backups crash lib lock mail run tmp
cache games local log opt spool www
thomas@
thomas@
_sbin_telinit.
_usr_bin_
_usr_bin_
_usr_bin_
_usr_bin_
_usr_lib_
_usr_lib_
_usr_sbin_
_usr_sbin_
thomas@
tdflanders (thomasdelbeke) wrote : | #10 |
thomas@
thomas@
* Stopping landscape-client daemon [ OK ]
* Reloading system message bus config... [ OK ]
* Starting the landscape-client daemon [ OK ]
thomas@
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:/
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:/
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:/
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@
* Stopping landscape-client daemon [ OK ]
* Reloading system message bus config... [ OK ]
* Starting the landscape-client daemon [ OK ]
thomas@
This script will interactively set u...
tdflanders (thomasdelbeke) wrote : | #11 |
thomas@
thomas@
backups crash lib lock mail run tmp
cache games local log opt spool www
thomas@
thomas@
_sbin_telinit.
_usr_bin_
_usr_bin_
_usr_bin_
_usr_bin_
_usr_lib_
_usr_lib_
_usr_sbin_
_usr_sbin_
thomas@
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.
-rw------- 1 thomas thomas 345139 2008-09-28 16:38 _usr_bin_
---------- 1 thomas thomas 1426237 2008-09-28 07:45 _usr_bin_
-rw------- 1 root root 37526 2008-09-28 10:20 _usr_bin_
-rw------- 1 root root 10536472 2008-09-28 12:03 _usr_bin_
---------- 1 thomas thomas 4252806 2008-09-29 17:21 _usr_lib_
-rw------- 1 thomas thomas 117781 2008-09-27 22:52 _usr_lib_
-rw------- 1 root root 231515 2008-09-29 22:16 _usr_sbin_
-rw------- 1 root root 2420554 2008-09-29 18:27 _usr_sbin_
thomas@
tdflanders (thomasdelbeke) wrote : | #12 |
thomas@
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://
100 /var/lib/
linux-source-
Installed: 2.6.27-4.6
Candidate: 2.6.27-4.6
Version table:
*** 2.6.27-4.6 0
500 http://
100 /var/lib/
linux-headers-
Installed: 2.6.27.4.4
Candidate: 2.6.27.4.4
Version table:
*** 2.6.27.4.4 0
500 http://
100 /var/lib/
linux-image-
Installed: 2.6.27.4.4
Candidate: 2.6.27.4.4
Version table:
*** 2.6.27.4.4 0
500 http://
100 /var/lib/
apport-gtk:
Installed: 0.116
Candidate: 0.116
Version table:
*** 0.116 0
500 http://
100 /var/lib/
landscape-client:
Installed: 1.0.21.1-0ubuntu1
Candidate: 1.0.21.1-0ubuntu1
Version table:
*** 1.0.21.1-0ubuntu1 0
500 http://
100 /var/lib/
W: Unable to locate package landscape-sysinfo
W: Unable to locate package landscape-config
W: Unable to locate package landscape
thomas@
tdflanders (thomasdelbeke) wrote : | #13 |
thomas@
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://
100 /var/lib/
linux-source-
Installed: 2.6.27-4.6
Candidate: 2.6.27-4.6
Version table:
*** 2.6.27-4.6 0
500 http://
100 /var/lib/
linux-headers-
Installed: 2.6.27.4.4
Candidate: 2.6.27.4.4
Version table:
*** 2.6.27.4.4 0
500 http://
100 /var/lib/
linux-image-
Installed: 2.6.27.4.4
Candidate: 2.6.27.4.4
Version table:
*** 2.6.27.4.4 0
500 http://
100 /var/lib/
apport-gtk:
Installed: 0.116
Candidate: 0.116
Version table:
*** 0.116 0
500 http://
100 /var/lib/
landscape-client:
Installed: 1.0.21.1-0ubuntu1
Candidate: 1.0.21.1-0ubuntu1
Version table:
*** 1.0.21.1-0ubuntu1 0
500 http://
100 /var/lib/
landscape-common:
Installed: 1.0.21.1-0ubuntu1
Candidate: 1.0.21.1-0ubuntu1
Version table:
*** 1.0.21.1-0ubuntu1 0
500 http://
100 /var/lib/
dpkg:
Installed: 1.14.20ubuntu6
Candidate: 1.14.20ubuntu6
Version table:
*** 1.14.20ubuntu6 0
500 http://
100 /var/lib/
thomas@
tdflanders (thomasdelbeke) wrote : | #14 |
thomas@
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:/
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:/
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:/
(22, 'Invalid argument')
Aborting Landscape configuration
* Reloading system message bus config... [ OK ]
tdflanders (thomasdelbeke) wrote : | #15 |
Hi there,
I could not reproduce this crash so far, but I managed to crash gnome-terminal with a nonsense pipe.
(thomas@
You fancy a gdb backtrace from this?
Cheers,
Thomas
Andreas Hasenack (ahasenack) wrote : | #16 |
Hi Thomas,
thanks for the info.
That landscape-
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!
tdflanders (thomasdelbeke) wrote : | #17 |
Hi Andreas,
please check this out (Bug #277208):
thomas@
Traceback (most recent call last):
File "/usr/bin/
sys.exit(run())
File "/usr/lib/
init_
File "/usr/lib/
handlers.
File "/usr/lib/
stream = open(filename, mode)
IOError: [Errno 13] Permission denied: '/var/log/
thomas@
But now:
thomas@
bash: cd: /var/log/
thomas@
thomas@
sysinfo.log
thomas@
thomas@
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@
tdflanders (thomasdelbeke) wrote : | #18 |
thomas@
bash: cd: /var/log/
thomas@
thomas@
sysinfo.log
thomas@
thomas@
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@
[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://
Get: 2 http://
Get: 3 http://
Fetched 179kB in 8s (22.2kB/s)
gpg: WARNING: unsafe ownership on configuration file `/home/
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_
dpkg-source: info: applying watchdog_
thomas@
bash: cd: /var/log/
thomas@
thomas@
bash: cd: /var/log/
thomas@
Removing `diversion of /bin/sh to /bin/sh.distrib by dash'
Removing `diversion of /usr/share/
thomas@
bash: cd: /var/log/
thomas@
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://
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_
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...
tdflanders (thomasdelbeke) wrote : | #19 |
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_
-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_
thomas@
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@
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://
Get: 2 http://
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-
Selecting previously deselected package landscape-common.
Unpacking landscape-common (from .../landscape-
Processing triggers for man-db ...
Setting up update-motd (1.8) ...
Setting up landscape-common (1.0.21.1-0ubuntu2) ...
thomas@
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-
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://
Get: 2 http://
Get: 3 http://
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-
Selecting previously deselec...
tdflanders (thomasdelbeke) wrote : | #20 |
thomas@
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_
-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_
thomas@
update-motd is now enabled.
/usr/sbin/
thomas@
tdflanders (thomasdelbeke) wrote : | #21 |
thomas@
update-motd is now enabled.
/usr/sbin/
thomas@
update-motd is now enabled.
thomas@
update-motd is now enabled.
/usr/sbin/
thomas@
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/
Aborting Landscape configuration
thomas@
/var/log/landscape
thomas@
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_
-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_
thomas@
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:/
thomas@
tdflanders (thomasdelbeke) wrote : | #22 |
thomas@
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:/
thomas@
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_
-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_
thomas@
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:/
thomas@
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:/
thomas@
error: must specify --url or the 'url' directive in the config file.
thomas@
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/
Aborting Landscape configuration
thomas@
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:/
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:/
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...
tdflanders (thomasdelbeke) wrote : | #23 |
- logfiles.iso Edit (98.0 KiB, application/x-iso9660-image)
thomas@
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_
-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_
-rw-r--r-- 1 root root 93 2008-10-14 05:36 watchdog.log
thomas@
[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@
Andreas Hasenack (ahasenack) wrote : | #24 |
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.
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.
tdflanders (thomasdelbeke) wrote : | #25 |
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/
I have gathered the following log data and compiled them into an iso (see above logfiles.iso):
/var/run/motd
/etc/default/
/var/log/
/var/log/
/var/log/
/var/log/
/var/log/
Can you verify if this is feasible?
Cheers,
Thomas
Andreas Hasenack (ahasenack) wrote : | #26 |
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.
Dimitrios Symeonidis (azimout) wrote : | #27 |
this bug report has not received any activity for a long time, is this still an issue?
fishears (johnnyp-ntlworld) wrote : Re: [Bug 270007] Re: landscape-sysinfo crashed with IOError in __init__() | #28 |
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
Andreas Hasenack (ahasenack) wrote : | #29 |
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!
Changed in landscape-client (Ubuntu): | |
status: | Incomplete → Invalid |
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 .landscape
ls -la /home/thomas/
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?