client reports wrong location of error log

Bug #292643 reported by ski on 2008-11-02
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
Low
Unassigned
landscape-client (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: landscape-client

Landscape reports the error log is in ~/.landscape/sysinfo.log , when in fact (at least on my machine) it is in /var/log/landscape/sysinfo.log. Intrepid Ibex, amd64. More info below:

  System information as of Sun Nov 2 09:50:01 EST 2008

  System load: 0.89 Swap usage: 0% Processes: 163
  Memory usage: 52% Temperature: 49 C Users logged in: 1

  => There were exceptions while processing one or more plugins. See
     ~/.landscape/sysinfo.log for more information.

  Graph this data and manage this system at https://landscape.canonical.com/
Last login: Sun Nov 2 09:48:25 2008 from deskaheh
ski@ganiodayo:~$ ls -l ~/.landscape/sysinfo.log
ls: cannot access /home/ski/.landscape/sysinfo.log: No such file or directory
ski@ganiodayo:~$ sudo ls -l /var/log/landscape/sysinfo.log
[sudo] password for ski:
-rw-r--r-- 1 landscape root 138129 2008-11-02 09:50 /var/log/landscape/sysinfo.log
ski@ganiodayo:~$

Andreas Hasenack (ahasenack) wrote :

Correct. When using update-motd to display the sysinfo output, the tool runs as root, and so the logs are in the central location in /var/log/landscape. When run everytime the user logs in, it runs with the user privileges, which means the logs are then located in ~/.landscape/sysinfo.log.

Changed in landscape-client:
status: New → Confirmed
importance: Undecided → Low
status: New → Confirmed

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

Landscape Team

Changed in landscape-client:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers