I was asked on IRC to capture the log files when the bug occurs. Thus, I have:
-Stopped all euca* services
-Rolled over all log files
-Rebooted system
I logged in and here is proof that eucalyptus-cc and uec-component-
listener are still not running.
Attached you will find all my log files:
Since I need to reinstall the system, I have made one final attempt at
capturing a clean set of logs:
I have:
-- Stopped euca*
-- Deleted everything under /var/log/eucalyptus
-- Started eucalyptus
-- Ran a series of commands (see everything after )
-- Stopped eucalyptus
The logs are
Here are my logs from the interaction above:
** Attachment added: euca_logs.tar.gz
http://launchpadlibrarian.net/50909571/euca_logs.tar.gz
--
eucalyptus-cc and uec-component-listener services are not started
https://bugs.launchpad.net/bugs/598182
You received this bug notification because
Please ignore comment #4 and comment #5, they were for another bug.
--
eucalyptus-cc and uec-component-listener services are not started
https://bugs.launchpad.net/bugs/598182
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
I was asked on IRC to capture the log files when the bug occurs. Thus, I have:
-Stopped all euca* services
-Rolled over all log files
-Rebooted system
I logged in and here is proof that eucalyptus-cc and uec-component-
listener are still not running.
Attached you will find all my log files:
Please ignore comment #1 it was meant for another bug.
--
Unable to register nodes in eucalyptus
https://bugs.launchpad.net/bugs/598186
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing
Since I need to reinstall the system, I have made one final attempt at
capturing a clean set of logs:
I have:
-- Stopped euca*
-- Deleted everything under /var/log/eucalyptus
-- Started eucalyptus
-- Ran a series of commands (see everything after )
-- Stopped eucalyptus
The logs are
I'm also uploading my configuration files.
** Attachment added: euca_conf.tar.gz
http://launchpadlibrarian.net/50910453/euca_conf.tar.gz
--
Unable to register nodes in eucalyptus
https://bugs.launchpad.net/bugs/598186
You received this bug notification because you are a member of Ubuntu
Why does the user have to provide anything custom in order to get more
value out of a product?
Having an easy way to reduce log verbosity (if the system is stable and
functioning) will help the user manage the system better by reducing the
noise. Why would a DEBUG log entry need to ever be
I'm also exhibiting the same problem, some of the background is here:
http://open.eucalyptus.com/forum/cc-not-able-registersee-nodes
--
Problems with node registration
https://bugs.launchpad.net/bugs/585108
You received this bug notification because you are a member of Ubuntu
Server Team, which
Public bug reported:
On Lucid, when the system starts, uec-component-listener and eucalyptus-
cc are not running.
List of my packages:
r...@srv-uec-qa-cc:/var/log/eucalyptus# dpkg -l|grep -i -e eucalyptus -e uec
ii euca2ools1.2-0ubuntu10
Public bug reported:
My topology is as follows: (Server names Corresponding coponents)
SRV-UEC-QA-CC: Contains CC, CLC, Walrus, SC
SRV-UEC-QA-NODE01: Contains NC
SRV-UEC-QA-NODE02: Contains NC
NOTE: I have another problem where eucalyptus-cc uec-component-
listener are not started by
The registration problem is filed as Bug #598186
--
eucalyptus-cc and uec-component-listener services are not started
https://bugs.launchpad.net/bugs/598182
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
I now have a clean install of UEC with apparmor working but it is a
problem if someone wants to remove it for whatever reason. This was a
test system and I was experimenting and I had assumed that UEC minus
apparmor was a supported configuration. Also, I wanted to have the
ability to have
Why is the status of the bug incomplete?
Are you unable to reproduce with the steps I mentioned?
--
Libvirtd -- error: monitor socket did not show up.: Connection refused
https://bugs.launchpad.net/bugs/585964
You received this bug notification because you are a member of Ubuntu
Server Team,
Patch to gracefully ignore Qcow-formatted images.
** Patch added: Patch to gracefully ignore Qcow-formatted images.
http://launchpadlibrarian.net/48774774/partition2disk_qcow.patch
--
NTFS partitions aren't properly detected in partition2disk
https://bugs.launchpad.net/bugs/494803
You
** Summary changed:
- NTFS partitions aren't properly detected in partition2disk
+ RAW images and NTFS aren't properly detected in partition2disk
** Summary changed:
- RAW images and NTFS aren't properly detected in partition2disk
+ Non-RAW images and NTFS aren't properly detected in
I am also getting the same exception.
Ubuntu 10.04 x64
08:36:27 DEBUG [ClusterNodeState:New I/O client worker #2-18] - BEFORE: [
m1.small available=8/8 c1.medium available=8/8 m1.large available=4/4 m1.xlarge
available=4/4 c1.xlarge available=2/2 ]
08:36:27 DEBUG [ClusterNodeState:New I/O
18 matches
Mail list logo
