Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - SamK

Pages: 1 [2]
Installation and Upgrades / ClamAV Warning
« on: May 08, 2009, 11:24:14 am »
After updating the packages and rebooting the following error message is received during the boot process,

Starting ClamAV daemon
LibclamAV Warning
This version of the ClamAV engine is outdated...

Is this significant?  Which logs should I post (if any)?

I am confused about the process by which eBox is updated and hoping to obtain some advice.

Software Management-->System Updates. 
This reports that the system is up to date.  How can this be tested as the eBox is a fresh install created May 06 2009 from a CD-ROM burned approximately two weeks ago.   When using an alternative Ubuntu PC apt-get update and upgrade indicates additional packages are available to install.

Installing eBox v 1 from CD-ROM entries are automatically placed in /etc/apt/sources.list referring to the CD-ROM and Ubuntu security repositories.  No other repositories were listed.  Is this correct?

How are updates obtained?  Which repositories are used?

What have I missed?

...An internal error related to a template has occurred. This is a bug, relevant information can be found in the logs.

Extract from ebox.log is attached.

The last change prior to receiving the error message was to enable NTP and assign 3 time-servers.

This post has been raised as I am not sure if the problem is related to the following post:

A non-exhaustive HOWTO showing the way in which a minimalist, lightweight GUI can be installed on an eBox machine.  This resulted from discussions in this thread:
It is suitable for use with the underlying Ubuntu 8.04-LTS Operating System and the entire download of files is approximately 110MB.  It is lightweight but this does not imply lightest possible.

  • Goals of the Installation
  • List of Packages & Purpose
  • Package Availability
  • Installing the Packages
  • Configuration
  • References

  • Use Open Source Software
  • Produce a lightweight GUI desktop capable of being run on low specification machines
  • The GUI to run reliably on an eBox + Ubuntu 8.04-LTS installation
  • Provide a locally installed web browser to enable access to the local eBox web-GUI
  • Provide a small selection of GUI tools
  • Provide a means of installing and/or removing packages via the GUI
  • Provide a means of updating the installed packages via the GUI
  • Provide 2-way remote control
  • Allow the look of the GUI to be modified
  • Require minimal post installation configuration

      Name                             Purpose
  • xserver-xorg-core     Provide an x server for GUI display
  • xinit                            Automatic starting of x server and session at bootup
  • menu                         Generate a 'start' menu of programs for menu aware applications
  • menu-xdg                  Convert Debian type menu structures to types
  • gdm                            Logon Manager
  • lxde                            Provide an (incomplete) suite of programs for management of a GUI environment
    Incuded in the meta-package for this version:
             openbox           Window Manager
             pcmanfm           Desktop & File Manager
             lxpanel              Desktop Panel Manager (Task Bar)
             lxsession-lite    Session Manager
             lxappearance   Theme Switcher
             xarchiver           File Compression/Decompression
             leafpad              Text Editor
             gpicview            Graphic File Viewer
    By recommendation
             gdm                    Logon Manager
  • lxnm                            Provides basic network information
  • lxterminal                   Provides a terminal emulator
  • lxtask                          Provides management of running processess, reports CPU and RAM usage
  • obconf                        Provides configuration of openbox preferences
  • openbox-themes      Provide a selection of themes for the Window Manager
  • grandr                         Provide VDU configuration
  • gdebi                           Installation of local *.deb packages, resolving and installing all dependencies
  • synaptic                      Provide a simplified GUI based display for apt package management
  • update-manager        Provide a simplifed GUI based display to install updates
  • firefox                          Provide a web browser to enable local access to eBox management controls
  • vinagre                        Enable a remote desktop to be controlled on a machine running tightvncserver
  • tightvncserver             Enable the local desktop to be controlled by a machine running vinagre
  • autocutsel                   Enable synchronization of the clipboard between local and remote machines
  • evince                         Enable reading of PDF files
  • pyneighborhood        Enable the browsing and mounting of shares on the network

1.  I wanted to have the same Ubuntu repositories available as those listed when installing from the official Ubuntu 8.04 LTS CD-ROM (i.e. excluding eBox).  When installing from the eBox v 1.0 CD-ROM only the security repositories were listed by default.
2. The deb-src repositories were not required for my installation and therefore manually commented out
3. Apart from the security repository the Ubuntu repositories for Great Britain are shown

Assume root credentials
Code: [Select]
sudo su

Edit the file governing repository access
Code: [Select]
nano /etc/apt/sources.list

Ensure the following entries are listed:
Code: [Select]
# deb cdrom:[Ubuntu-Server 8.04.2 _Hardy Heron_ - Release i386 (20090121.1)]/ hardy extras main restricted
# deb cdrom:[Ubuntu-Server 8.04.2 _Hardy Heron_ - Release i386 (20090121.1)]/pool/extras/ /

deb hardy-security main restricted
# deb-src hardy-security main restricted
deb hardy-security universe
# deb-src hardy-security universe
deb hardy-security multiverse
# deb-src hardy-security multiverse

deb hardy main restricted
# deb-src hardy main restricted

## Major bug fix updates produced after the final release of the distribution.
deb hardy-updates main restricted
# deb-src hardy-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in universe
## WILL NOT receive any review or updates from the Ubuntu security team.
deb hardy universe
# deb-src hardy universe
deb hardy-updates universe
# deb-src hardy-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb hardy multiverse
# deb-src hardy multiverse
deb hardy-updates multiverse
# deb-src hardy-updates multiverse

## Uncomment the following two lines to add software from the 'backports'repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
# deb hardy-backports main restricted universe multiverse
# deb-src hardy-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository. This software is not part of Ubuntu, but is offered
## by Canonical and the respective vendors as a service to Ubuntu users.
deb hardy partner
# deb-src hardy partner

deb hardy main

deb hardy main

Ensure Packages from the Repositories are Available
Code: [Select]
apt-get update

1. apptitude is used as, by default, it installs the specified packages together with any recommended by them

Install the GUI packages and tools
Code: [Select]
aptitude --assume-yes install [list of packages detailed in Packages by Name]
aptitude --assume-yes install xserver-xorg-core xinit menu ...etc

Verify the installation is complete by checking for broken dependencies
Code: [Select]
apt-get check

Restart the machine to display a GUI logon screen
Code: [Select]
shutdown -r now

1. Packages which require configuration to function are shown
2. Packages which provide cosmetic configuration are not shown
3. The following configurations should be performed with root credentials


Automatically start at bootup
Edit /root/.vnc/xstartup
Add the following lines
Code: [Select]
# Enable synchronization of the local & remote clipboards
autocutsel -fork &

1. After configuration the eBox web-gui can be started by entering in the Firefox Address Bar

Provide a Menu Icon
Edit /usr/share/applications/firefox.desktop  (Displayed as Firefox Web Browser)
Change the Icon= to the following
Code: [Select]


Provide a menu icon
Create /usr/share/applications/grandr.desktop
Add the following lines:
Code: [Select]
[Desktop Entry]
Name=Monitor Resolution Settings
Comment=Configure VDU Display
Categories=Settings; System;

1. After configuration the tightvncserver can be contacted from a client running vinagre by entering the server-ip-address:5909 in the vinagre Connect-->Host field
2. A remote session to the server will start with root credentials

Generate the Configuration Files for Desktop Number 9
Conduct as root in an LXterminal window
Code: [Select]
vncserver :9create a password when requested

Set Up the Desktop to Display on a Remote Client
Edit /root/.vnc/xstartup to contain the following
Code: [Select]
# Set the resources to be used by the xserver
xrdb $HOME/.Xresources

# set the desktop colour
xsetroot -solid grey

# Set the defaults for the terminal window
x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &

# Start the window manager
#x-window-manager &
openbox &

# Display the GUI panel
lxpanel &

Specify the Default Screen Resolution for Remote Clients Connecting to the Server
Edit /usr/bin/tightvncserver
Code: [Select]
Comment out $geometry = "1074x768";
Add the line $geometry = "800x600";

Ensure a Server Session Automatically Starts at Bootup
Edit /etc/rc.local
Add the lines
Code: [Select]
# Start TightVNCServer at bootup
su --command="tightvncserver :9"   root


Installation and Upgrades / A GUI For an eBox Machine?
« on: May 01, 2009, 04:33:38 pm »
While exploring eBox, some connection difficulties were experienced which prevented the eBox web-gui from being shown.  In trouble-shooting the problems I found it helpful to have a locally installed web browser, which in turn, required the installation of a GUI environment.

I fully understand that this is not needed in order to successfully use eBox.  Users will operate eBox via its web-gui and sys-admins will manage the machine via the command line.  It might help new users eBox have a more comfortable intoduction to eBox.

The GUI I used is suitable for older less powerful installations.  It is light in its use of system resources, has a small disk footprint and includes a small selection of gui tools.  It is quite spartan and is not meant to be an 'all-singing-all-dancing' desktop.

It was helpful for me and I am willing to post further information if it is of interest or value to others.  I will not be able to offer support or guidance on how configure it; I have simply gathered together freely available components to meet my needs.

Having trouble getting a working configuration for DHCP in eBox and am hoping to to get some advice.  The LAN workstation does not recieve an ip address from the eBox Machine.

ip address=
DHCP Status=Disabled

eBox Machine
Single NIC installed=eth0
Module Status
  • DHCP=Enabled
  • DNS=Disabled
  • DHCP=Running
  • eth0=Static

  • Custom Gateway=
  • Domain=Blank
  • Custom Nameserver=
  • IP Address=
  • Subnet=
  • Available Range=
All changes saved without errors

From the eBox Machine

From the LAN Workstation (Dynamic IP DHCP)
ifconfig=ip address not allocated

From the LAN Workstation (Static IP Locally Set)

I've gone 'snow-blind' on this and simply cannot see the answer.

Installation and Upgrades / Request Help Resolving LAN Names and IPs
« on: April 22, 2009, 04:48:37 pm »
Hoping to find some advice on how to get DNS working.  At this stage only resolution of names/address on the LAN is needed not registering a domain with an external provider.

DNS as provided by ISP
DHCP for LAN providing reserved/static IPs for servers and dynamic IPs for workstations

IPAddress= (static)

Dashboard reports DNS as Running
Module Status reports DNS as enabled (ticked)
DNS created Domain=TESTDOM, IPAddress=
DNS-->Hostname=Ubu810Min, IPAddress= (dynamic) Workstation on LAN
Network-->DNS reports 1st Nameserver=, 2nd Nameserver= (reordered to place eBox 1st)


lookuo TESTDOM=; <<>> DiG 9.4.2-P2 <<>> +time=3 TESTDOM
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21267
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;TESTDOM.         IN   A

.         8679   IN   SOA   A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2009042200 1800 900 604800 86400

;; Query time: 16 msec
;; WHEN: Wed Apr 22 15:38:43 2009
;; MSG SIZE  rcvd: 100

cat /etc/resolv.conf
Is this correct? Should have been added by eBox?

Resolution via the WAN (ISP DNS) is working OK but not inside the LAN.

On a clean install from eBox CD-ROM and applying updates available as at 21 April 2009, the following occurs when attempting to activate DNS.

Module Status-->Tick DNS to activate, save changes and confirm changes to be saved.  The save routine generates the following error message:
"Some modules reported error when saving changes. More information on the logs in /var/log/ebox   
The following modules failed while saving their changes"
No modules are listed.

Attached is /var/log/ebox/ebox.log
The following logs are 258Kb & 147Kb respectively and are over the size limit allowed for attachments.

The Dashboard shows DNS as running and Module Status shows DNS as ticked.

A Domain name of TESTDOM is added and saved without errors.
Adding a hostname generates the same error message as shown above.

Is anyone able to advise what is causing the problem and how to resolve it?

On a test bench machine a clean install of eBox Platform v 1.0 has been conducted using a CD-ROM created from the current ISO.  The two stage process seems to complete successfully.

Each time the machine is rebooted it reports the root file system was not cleanly unmounted and runs fsck.  The machine then reboots at the request of fsck and successfully completes the boot up sequence and works as expected.  This pattern of behavior is repeated each time the machine is shut down using the commands "shutdown -h now" or "shutdown -r now".

As a check, the machine has been rebuilt to the same specifications but using the official Ubuntu 804.2-Server LTS installation media.  The full ebox Platform was then installed from the launchpad repository using "^ebox-.*".  The resulting installation does not require the check of the file system each time the machine is rebooted.

To create a production machine, an installation using the eBox installation CD-ROM is preferred.  Assistance is requested in understanding and resolving the current issue.

  • What is the reason for the difference in behavior?
  • How can the installation conducted using the eBox ISO be changed to stop the file system check running at each reboot?

Pages: 1 [2]