[Bug 1278466] Re: [FFe] ceph firefly stable release

[Shang Wu]

Will 0.80 be supported for 5 years ?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1278466

Title:
  [FFe] ceph firefly stable release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1278466/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1320733] [NEW] Broken vagrant download link on juju docs website

[Shang Wu]

Public bug reported:

On https://juju.ubuntu.com/docs/config-vagrant.html page, there are
14.04 and 12.04 image files you can download directly. However, 14.04 is
broken.

The current one points to :

http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-
cloudimg-amd64-juju-vagrant-disk1.box

And it should be

http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-
cloudimg-amd64-vagrant-disk1.box

Same thing goes to the i386

** Affects: juju (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1320733

Title:
  Broken vagrant download link on juju docs website

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1320733/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"

[Shang Wu]

The reason for the error is because node couldn't get to the Internet.
Issue fixed by configuring the proxy to the MAAS server.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1237364

Title:
  Commissioning with a Saucy image sets node status to "Failed tests"

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"

[Shang Wu]

We ran into this issue on 14.04. 
maas version: 1.4+bzr1820+dfsg-0ubuntu1
deploy 12.04.3 images

Error output
failed [2/5] ( 00-maas-01-lshw 00-maas-02-virtuality)


  
 Desktop Computer
 (To be filled by O.E.M.)
 64
 
  
  
  
  
  
 
 
  SMBIOS version 2.7
  DMI version 2.7
  32-bit processes
 
  
   Motherboard
   D53427RKE
   Intel Corporation
   0
   G87790-403
   GERK34400GZZ
   To be filled by O.E.M.

 BIOS
 Intel Corp.
 0
 RKPPT10H.86A.0017.2013.0425.1251
 04/25/2013
 65536
 16711680
 
  PCI bus
  BIOS EEPROM can be 
upgraded
  BIOS shadowing
  Booting from CD-ROM/DVD
  Selectable boot path
  Enhanced Disk Drive extensions
  5.25" 1.2MB floppy
  3.5" 720KB floppy
  3.5" 2.88MB floppy
  Print Screen key
  INT14 serial line 
control
  INT17 printer control
  ACPI
  USB legacy emulation
  BIOS boot 
specification
 


 L2 cache
 3d
 CPU Internal L2
 524288
 524288
 
  Internal
  Write-trough
  Unified cache
 


 L1 cache
 3e
 CPU Internal L1
 131072
 131072
 
  Internal
  Write-trough
  Data cache
 


 L3 cache
 3f
 CPU Internal L3
 3145728
 3145728
 
  Internal
  Write-back
  Unified cache
 


 System Memory
 40
 System board or motherboard
 17179869184
  
   SODIMM DDR3 Synchronous 1600 MHz (0.6 
ns)
   9905428-087.A00LF
   Kingston
   0
   2B130439
   DIMM1
   8589934592
   64
   16
  
  
   SODIMM DDR3 Synchronous 1600 MHz (0.6 
ns)
   9905428-087.A00LF
   Kingston
   1
   2D130939
   DIMM2
   8589934592
   64
   16
  


 CPU
 Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz
 Intel Corp.
 41
 cpu@0
 Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz
 CPU 1
 18
 28
 64
 1
 
  
  
  
 
 
  64bits extensions (x86-64)
  mathematical co-processor
  FPU exceptions 
reporting
  
  virtual mode extensions
  debugging extensions
  page size extensions
  time stamp counter
  model-specific registers
  4GB+ memory addressing (Physical Address 
Extension)
  machine check exceptions
  compare and exchange 8-byte
  on-chip advanced programmable interrupt 
controller (APIC)
  fast system calls
  memory type range registers
  page global enable
  machine check architecture
  conditional move instruction
  page attribute table
  36-bit page size extensions
  
  debug trace and EMON store 
MSRs
  thermal control (ACPI)
  multimedia extensions (MMX)
  fast floating point 
save/restore
  streaming SIMD extensions 
(SSE)
  streaming SIMD extensions 
(SSE2)
  self-snoop
  HyperThreading
  thermal interrupt and status
  pending break event
  fast system calls
  no-execute bit (NX)
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  CPU Frequency scaling
 


 Host bridge
 3rd Gen Core processor DRAM Controller
 Intel Corporation
 100
 pci@:00:00.0
 09
 32
 3300
 
  
 
 
  
 
  
   VGA compatible controller
   3rd Gen Core processor Graphics Controller
   Intel Corporation
   2
   pci@:00:02.0
   09
   64
   3300
   

   
   
Message Signalled Interrupts
Power Management

bus mastering
PCI capabilities 
listing
   
   



   
  
  
   USB controller
   7 Series/C210 Series Chipset Family USB xHCI Host 
Controller
   Intel Corporation
   14
   pci@:00:14.0
   04
   64
   3300
   


   
   
Power Management
Message Signalled Interrupts

bus mastering
PCI capabilities 
listing
   
   


   
  
  
   Communication controller
   7 Series/C210 Series Chipset Family MEI Controller 
#1
   Intel Corporation
   16
   pci@:00:16.0
   04
   64
   3300
   


   
   
Power Management
Message Signalled Interrupts
bus mastering
PCI capabilities 
listing
   
   


   
  
  
   Serial controller
   7 Series/C210 Series Chipset Family KT 
Controller
   Intel Corp

[Bug 1070190] [NEW] maas-enlist does not show on latest 12.04.1

[Shang Wu]

Public bug reported:

Issue:
A fresh installed maas with latest updates will not have maas-enlist shows up 
on the maas menu.

Steps to reproduce:

1. Fresh install maas with latest update to 12.04.1

2. Install the necessary packages:
$ sudo apt-get install maas
$ sudo apt-get install maas-dhcp
$ sudo maas-import-isos

3. Reboot

4. Check the maas menu by running the command:

$ sudo cobbler profile list

5. It only shows:

profiles:
   maas-precise-i386
   maas-precise-i386-commissioning
   maas-precise-x86_64
   maas-precise-x86_64-commissioning
   precise-i386
   precise-i386-auto
   precise-x86_64
   precise-x86_64-auto

Root Cause:

After enabling the -x in the maas-import-isos, it gives the error below:

+ PARENT_PROFILE=quantal-i386
+ grep -qs  maas-enlist
+ cobbler profile list
+ cobbler profile add --name=maas-enlist --parent=quantal-i386 
--kopts=priority=critical locale=en_US netcfg/choose_interface=auto 
log_host=10.232.36.101 log_port=514 
--kickstart=/var/lib/cobbler/kickstarts/maas-enlist.preseed
profile quantal-i386 not found, inheritance not possible
+ grep -qs  default
+ cobbler system list
+ cobbler system add --name=default --profile=maas-enlist
invalid profile name: maas-enlist
+ cobbler sync

Workaround:

Open the file /usr/sbin/maas-import-isos with your favourite editor, at
line 106, Where it says STABLE=$(distro-info --stable), change it to
"precise"

add_enlist_profile(){
STABLE=precise
DEVEL=$(distro-info --devel)

Run the command again, then the issue is resolved.


P.S. Credit to Dann Frazier's help to solve this issue.

** Affects: maas (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Issue:
  A fresh installed maas with latest updates will not have maas-enlist shows up 
on the maas menu.
  
  Steps to reproduce:
  
  1. Fresh install maas with latest update to 12.04.1
  
  2. Install the necessary packages:
  $ sudo apt-get install maas
  $ sudo apt-get install maas-dhcp
- $ sudo maas-import-isos 
+ $ sudo maas-import-isos
  
  3. Reboot
  
  4. Check the maas menu by running the command:
  
  $ sudo cobbler profile list
  
  5. It only shows:
  
  profiles:
-maas-precise-i386
-maas-precise-i386-commissioning
-maas-precise-x86_64
-maas-precise-x86_64-commissioning
-precise-i386
-precise-i386-auto
-precise-x86_64
-precise-x86_64-auto
+    maas-precise-i386
+    maas-precise-i386-commissioning
+    maas-precise-x86_64
+    maas-precise-x86_64-commissioning
+    precise-i386
+    precise-i386-auto
+    precise-x86_64
+    precise-x86_64-auto
  
  Root Cause:
  
  After enabling the -x in the maas-import-isos, it gives the error below:
  
  + PARENT_PROFILE=quantal-i386
  + grep -qs  maas-enlist
  + cobbler profile list
  + cobbler profile add --name=maas-enlist --parent=quantal-i386 
--kopts=priority=critical locale=en_US netcfg/choose_interface=auto 
log_host=10.232.36.101 log_port=514 
--kickstart=/var/lib/cobbler/kickstarts/maas-enlist.preseed
  profile quantal-i386 not found, inheritance not possible
  + grep -qs  default
  + cobbler system list
  + cobbler system add --name=default --profile=maas-enlist
  invalid profile name: maas-enlist
  + cobbler sync
  
  Workaround:
  
  Open the file /usr/sbin/maas-import-isos with your favourite editor, at
  line 106, Where it says STABLE=$(distro-info --stable), change it to
  "precise"
  
  add_enlist_profile(){
- STABLE=precise
- DEVEL=$(distro-info --devel)
+ STABLE=precise
+ DEVEL=$(distro-info --devel)
  
  Run the command again, then the issue is resolved.
+ 
+ 
+ P.S. Credit to Dann Frazier's help to solve this issue.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1070190

Title:
  maas-enlist does not show on latest 12.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1070190/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 392236] Re: MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS

[Shang Wu]

Seems to be directly related to:
http://bugs.mysql.com/bug.php?id=21476

** Bug watch added: MySQL Bug System #21476
   http://bugs.mysql.com/bug.php?id=21476

-- 
MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS
https://bugs.launchpad.net/bugs/392236
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 394036] Re: MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...)

[Shang Wu]

Seems to be directly related to:
http://bugs.mysql.com/bug.php?id=21476

** Bug watch added: MySQL Bug System #21476
   http://bugs.mysql.com/bug.php?id=21476

-- 
MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...)
https://bugs.launchpad.net/bugs/394036
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 394036] [NEW] MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS (SELECT 0+0+0...)

[Shang Wu]

Public bug reported:

Fresh install dapper 6.06.2 with latest updates. Running MySQL Version:
5.0.22-0ubuntu6.06.11 on the system.

Using the default my.cnf  with one setting changed:
thread_stack = 265K

Running the following MySQL command:
mysql> SELECT 
0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0+0;
Then we get the error:
ERROR 2013 (HY000): Lost connection to MySQL server during query

>From syslog, it show:

Jun 30 10:00:39 ubuntu mysqld[14953]: mysqld got signal 11;
Jun 30 10:00:39 ubuntu mysqld[14953]: This could be because you hit a bug. It 
is also possible that this binary
Jun 30 10:00:39 ubuntu mysqld[14953]: or one of the libraries it was linked 
against is corrupt, improperly built,
Jun 30 10:00:39 ubuntu mysqld[14953]: or misconfigured. This error can also be 
caused by malfunctioning hardware.
Jun 30 10:00:39 ubuntu mysqld[14953]: We will try our best to scrape up some 
info that will hopefully help diagnose
Jun 30 10:00:39 ubuntu mysqld[14953]: the problem, but since we have already 
crashed, something is definitely wrong
Jun 30 10:00:39 ubuntu mysqld[14953]: and this may fail.
Jun 30 10:00:39 ubuntu mysqld[14953]: 
Jun 30 10:00:39 ubuntu mysqld[14953]: key_buffer_size=16777216
Jun 30 10:00:39 ubuntu mysqld[14953]: read_buffer_size=131072
Jun 30 10:00:39 ubuntu mysqld[14953]: max_used_connections=1
Jun 30 10:00:39 ubuntu mysqld[14953]: max_connections=100
Jun 30 10:00:39 ubuntu mysqld[14953]: threads_connected=1
Jun 30 10:00:39 ubuntu mysqld[14953]: It is possible that mysqld could use up 
to 
Jun 30 10:00:39 ubuntu mysqld[14953]: key_buffer_size + (read_buffer_size + 
sort_buffer_size)*max_connections = 233983 K
Jun 30 10:00:39 ubuntu mysqld[14953]: bytes of memory
Jun 30 10:00:39 ubuntu mysqld[14953]: Hope that's ok; if not, decrease some 
variables in the equation.
Jun 30 10:00:39 ubuntu mysqld[14953]: 
Jun 30 10:00:39 ubuntu mysqld[14953]: thd=0x8b0d238
Jun 30 10:00:39 ubuntu mysqld[14953]: Attempting backtrace. You can use the 
following information to find out
Jun 30 10:00:39 ubuntu mysqld[14953]: where mysqld died. If you see no messages 
after this, something went
Jun 30 10:00:39 ubuntu mysqld[14953]: terribly wrong...
Jun 30 10:00:39 ubuntu mysqld[14953]: Cannot determine thread, fp=0xb3f54d48, 
backtrace may not be correct.
Jun 30 10:00:39 ubuntu mysqld[14953]: Stack range sanity check OK, backtrace 
follows:
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x818a089
Jun 30 10:00:39 ubuntu mysqld[14953]: 0xe420
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x8b2d890
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x81d24e4
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x81d2877
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x81d40cd
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x81e6609
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x8279856
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x827b172
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x827afae
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x81c2c21
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x819d205
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x81a2ce7
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x81a32b1
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x81a43ec
Jun 30 10:00:39 ubuntu mysqld[14953]: 0x81a4d98
Jun 30 10:00:39 ubuntu mysqld[14953]: 0xb7f1c341
Jun 30 10:00:39 ubuntu mysqld[14953]: 0xb7d6d4ee
Jun 30 10:00:39 ubuntu mysqld[14953]: New value of fp=(nil) failed sanity 
check, terminating sta

[Bug 392236] [NEW] MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS

[Shang Wu]

Public bug reported:

System info:
r...@cmdb:~# dpkg -l mysql-server-5.0
ii mysql-server-5.0 5.0.22-0ubuntu6.06.11 mysql database server binaries
r...@cmdb:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 6.06.2 LTS
Release: 6.06
Codename: dapper

Using the following query triger the crash on the dapper 6.06.2 machine:
Result from MySQL 5.0.22 (Ubuntu)
r...@localhost:(none)> SELECT * FROM (SELECT mu.User FROM mysql.user mu UNION 
SELECT mu.user FROM mysql.user mu ORDER BY mu.user) a;
ERROR 2013 (HY000): Lost connection to MySQL server during query
r...@localhost:(none)> SELECT * FROM (SELECT mu.User FROM mysql.user mu UNION 
SELECT mu.user FROM mysql.user mu) a;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 1
Current database: *** NONE ***
+--+
| User |
+--+
| debian-sys-maint |
| root |
+--+
5 rows in set (0.00 sec)

However, the issue does not exist in Debian:
Result from MySQL 5.0.81 (Debian)
r...@localhost:(none)> SELECT * FROM (SELECT mu.User FROM mysql.user mu UNION 
SELECT mu.user FROM mysql.user mu ORDER BY mu.user) a;
ERROR 1054 (42S22): Unknown column 'mu.user' in 'order clause' 

More debug info:
Jun 23 16:09:57 cmdb mysqld[21409]: mysqld got signal 11;
Jun 23 16:09:57 cmdb mysqld[21409]: This could be because you hit a bug. It is 
also possible that this binary
Jun 23 16:09:57 cmdb mysqld[21409]: or one of the libraries it was linked 
against is corrupt, improperly built,
Jun 23 16:09:57 cmdb mysqld[21409]: or misconfigured. This error can also be 
caused by malfunctioning hardware.
Jun 23 16:09:57 cmdb mysqld[21409]: We will try our best to scrape up some info 
that will hopefully help diagnose
Jun 23 16:09:57 cmdb mysqld[21409]: the problem, but since we have already 
crashed, something is definitely wrong
Jun 23 16:09:57 cmdb mysqld[21409]: and this may fail.
Jun 23 16:09:57 cmdb mysqld[21409]:
Jun 23 16:09:57 cmdb mysqld[21409]: key_buffer_size=67108864
Jun 23 16:09:57 cmdb mysqld[21409]: read_buffer_size=131072
Jun 23 16:09:57 cmdb mysqld[21409]: max_used_connections=1
Jun 23 16:09:57 cmdb mysqld[21409]: max_connections=100
Jun 23 16:09:57 cmdb mysqld[21409]: threads_connected=1
Jun 23 16:09:57 cmdb mysqld[21409]: It is possible that mysqld could use up to
Jun 23 16:09:57 cmdb mysqld[21409]: key_buffer_size + (read_buffer_size + 
sort_buffer_size)*max_connections = 283135 K
Jun 23 16:09:57 cmdb mysqld[21409]: bytes of memory
Jun 23 16:09:57 cmdb mysqld[21409]: Hope that's ok; if not, decrease some 
variables in the equation.
Jun 23 16:09:57 cmdb mysqld[21409]:
Jun 23 16:09:57 cmdb mysqld[21409]: thd=0x8b0e230
Jun 23 16:09:57 cmdb mysqld[21409]: Attempting backtrace. You can use the 
following information to find out
Jun 23 16:09:57 cmdb mysqld[21409]: where mysqld died. If you see no messages 
after this, something went
Jun 23 16:09:57 cmdb mysqld[21409]: terribly wrong...
Jun 23 16:09:57 cmdb mysqld[21409]: Cannot determine thread, fp=0xb1037d48, 
backtrace may not be correct.
Jun 23 16:09:57 cmdb mysqld[21409]: Stack range sanity check OK, backtrace 
follows:
Jun 23 16:09:57 cmdb mysqld[21409]: 0x818a089
Jun 23 16:09:57 cmdb mysqld[21409]: 0xe420
Jun 23 16:09:57 cmdb mysqld[21409]: 0x8b9e4f0
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81d24e4
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81d2877
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81d40cd
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81e6609
Jun 23 16:09:57 cmdb mysqld[21409]: 0x8279856
Jun 23 16:09:57 cmdb mysqld[21409]: 0x827b172
Jun 23 16:09:57 cmdb mysqld[21409]: 0x827afae
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81c2c21
Jun 23 16:09:57 cmdb mysqld[21409]: 0x819d205
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81a2ce7
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81a32b1
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81a43ec
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81a4d98
Jun 23 16:09:57 cmdb mysqld[21409]: 0xb7ed1341
Jun 23 16:09:57 cmdb mysqld[21409]: 0xb7d224ee
Jun 23 16:09:57 cmdb mysqld[21409]: New value of fp=(nil) failed sanity check, 
terminating stack trace!
Jun 23 16:09:57 cmdb mysqld[21409]: Please read 
http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow 
instructions on how to resolve the stack trace. Resolved
Jun 23 16:09:57 cmdb mysqld[21409]: stack trace is much more helpful in 
diagnosing the problem, so please do
Jun 23 16:09:57 cmdb mysqld[21409]: resolve it
Jun 23 16:09:57 cmdb mysqld[21409]: Trying to get some variables.
Jun 23 16:09:57 cmdb mysqld[21409]: Some pointers may be invalid and cause the 
dump to abort...
Jun 23 16:09:57 cmdb mysqld[21409]: thd->query at 0x8b15f40 = SELECT * FROM 
(SELECT c.cid,sd.hostname,r.name AS rack,l.name AS location,r.rid,sd.height AS 
top_height,m.height AS height, IF(m.heightthread_id=8
Jun 23 16:09:57 cmdb mysqld[21409]: The manual page at 
http://www.mysql.com/doc/en/Crashing.html contains
Jun 23 16:09:57 cmdb mysqld[21409]: information that should help you find

[Bug 250847] Re: Apache predefined script in redhat-cluster-suite is not properly setup for Ubuntu

[Shang Wu]

Thanks Ante!

This fixes the issue.

-- 
Apache predefined script in redhat-cluster-suite is not properly setup for 
Ubuntu
https://bugs.launchpad.net/bugs/250847
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 250847] Re: Apache predefined script in redhat-cluster-suite is not properly setup for Ubuntu

[Shang Wu]

** Attachment added: "httpd-parse-config.pl"
   http://launchpadlibrarian.net/16234999/httpd-parse-config.pl

-- 
Apache predefined script in redhat-cluster-suite is not properly setup for 
Ubuntu
https://bugs.launchpad.net/bugs/250847
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to redhat-cluster-suite in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 250847] Re: Apache predefined script in redhat-cluster-suite is not properly setup for Ubuntu

[Shang Wu]

** Attachment added: "cluster.conf"
   http://launchpadlibrarian.net/16234994/cluster.conf

-- 
Apache predefined script in redhat-cluster-suite is not properly setup for 
Ubuntu
https://bugs.launchpad.net/bugs/250847
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to redhat-cluster-suite in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 250847] Re: Apache predefined script in redhat-cluster-suite is not properly setup for Ubuntu

[Shang Wu]

** Attachment added: "apache.sh"
   http://launchpadlibrarian.net/16234984/apache.sh

-- 
Apache predefined script in redhat-cluster-suite is not properly setup for 
Ubuntu
https://bugs.launchpad.net/bugs/250847
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to redhat-cluster-suite in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 250847] [NEW] Apache predefined script in redhat-cluster-suite is not properly setup for Ubuntu

[Shang Wu]

Public bug reported:

Background:
I tried to setup the apache server using redhat-cluster-suite on three machines 
running Hardy. The apache server can be started on any single machine without 
any error, but not using the redhat-cluster-suite to start the apache service.

Symptom:
Once the apache service started from the redhat-cluster-suite, it will stated 
as start for 5 seconds and tried to restart again.

The log message (/var/log/syslog) looks like the following:
Jul 22 10:26:20 c3 clurgmgrd[6529]:  Service service:Apache2 started 
Jul 22 10:26:24 c3 clurgmgrd: [6529]:  script:Web Services: status of 
/etc/init.d/apache2 failed (returned 1) 
Jul 22 10:26:24 c3 clurgmgrd[6529]:  status on script "Web Services" 
returned 1 (generic error) 
Jul 22 10:26:24 c3 clurgmgrd[6529]:  Stopping service service:Apache2 
Jul 22 10:26:24 c3 clurgmgrd[6529]:  Service service:Apache2 is 
recovering 
Jul 22 10:26:24 c3 clurgmgrd[6529]:  Recovering failed service 
service:Apache2 
Jul 22 10:26:24 c3 clurgmgrd[6529]:  Service service:Apache2 started 

What I have tried:
I looked at the /usr/share/cluster/apache.sh file and found 1 obvious error at 
line 43 where it says:
declare APACHE_genConfig="$APACHE_conf_dir/httpd.conf"
In Ubuntu, that file (httpd.conf) is empty. I changed that to apache2.conf, but 
still have the same issue.

Also, in the same file at line 142 where it says:
for i in `"$APACHE_parseConfig" -D"$OCF_RESKEY_name" < 
"$originalConfigFile" | grep -E '(^Listen)|(^Port)' | grep -v ':'`; do 
This refer to another file which will need some fixes too.

Hope this helps,

** Affects: redhat-cluster-suite (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Apache predefined script in redhat-cluster-suite is not properly setup for 
Ubuntu
https://bugs.launchpad.net/bugs/250847
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to redhat-cluster-suite in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 134440] Re: P5: Changed date cannot be kept, will be changed back on resume

[Shang Wu]

Unable to follow-up with the client. Case closed.

** Changed in: dhcp3 (Ubuntu)
   Status: Incomplete => Invalid

-- 
P5: Changed date cannot be kept, will be changed back on resume
https://bugs.launchpad.net/bugs/134440
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs