Problem in EC2 upload of OpenSuse 12.1 (JeOS) 32 bits

[hgomez]

Hi to all,

I tried many time today to upload to EC2 a very basic OpenSuse 12.1
(JeOS) 32 bits to my AWS Account.

AWS create SNAPSHOT but AMI can't be created and Studio Fail in Timeout.

I see a thread with a similar problem "My SUSEStudio buit EC2 AMI wont
stop "initializing"

Did "yast2-firstboot" hack is still needed ?

Cheers

[Raphael Lydia Bertoche]

I had the same problem. Got it solved (in an ugly way) using sysvinit instead of systemd.
http://susestudio.com/a/MPE71Z/aws-opensuse-121-with-sysvinit-x86

Raphael
<a href="tel:%2821%29%209162%205605" value="[phone]" target="_blank">(21) 9162 5605
<a href="tel:%2821%29%203527%202253" value="[phone]" target="_blank">(21) 3527 2253

On 2 April 2012 19:18, Henri Gomez <[hidden email]> wrote:

Hi to all,

I tried many time today to upload to EC2 a very basic OpenSuse 12.1
(JeOS) 32 bits to my AWS Account.

AWS create SNAPSHOT but AMI can't be created and Studio Fail in Timeout.

I see a thread with a similar problem "My SUSEStudio buit EC2 AMI wont
stop "initializing"

Did "yast2-firstboot" hack is still needed ?

Cheers

[hgomez]

Did problem appears only for x86 (32bits) OpenSuse 12.1 appliance ?

I did a JeOS 12.1 64bits and didn't get such problem

2012/4/3 Raphael Lydia Bertoche <[hidden email]>:

> I had the same problem. Got it solved (in an ugly way) using sysvinit
> instead of systemd.
> http://susestudio.com/a/MPE71Z/aws-opensuse-121-with-sysvinit-x86
>
> Raphael
> (21) 9162 5605
> (21) 3527 2253
>
>
>
> On 2 April 2012 19:18, Henri Gomez <[hidden email]> wrote:
>>
>> Hi to all,
>>
>> I tried many time today to upload to EC2 a very basic OpenSuse 12.1
>> (JeOS) 32 bits to my AWS Account.
>>
>> AWS create SNAPSHOT but AMI can't be created and Studio Fail in Timeout.
>>
>> I see a thread with a similar problem "My SUSEStudio buit EC2 AMI wont
>> stop "initializing"
>>
>> Did "yast2-firstboot" hack is still needed ?
>>
>> Cheers
>
>

[Raphael Lydia Bertoche]

No, I had this problem with x86_64.

On 3 April 2012 06:27, Henri Gomez <[hidden email]> wrote:

Did problem appears only for x86 (32bits) OpenSuse 12.1 appliance ?

I did a JeOS 12.1 64bits and didn't get such problem

2012/4/3 Raphael Lydia Bertoche <[hidden email]>:

> I had the same problem. Got it solved (in an ugly way) using sysvinit
> instead of systemd.
> http://susestudio.com/a/MPE71Z/aws-opensuse-121-with-sysvinit-x86
>
> Raphael
> <a href="tel:%2821%29%209162%205605" value="[phone]">(21) 9162 5605
> <a href="tel:%2821%29%203527%202253" value="[phone]">(21) 3527 2253
>
>
>
> On 2 April 2012 19:18, Henri Gomez <[hidden email]> wrote:
>>
>> Hi to all,
>>
>> I tried many time today to upload to EC2 a very basic OpenSuse 12.1
>> (JeOS) 32 bits to my AWS Account.
>>
>> AWS create SNAPSHOT but AMI can't be created and Studio Fail in Timeout.
>>
>> I see a thread with a similar problem "My SUSEStudio buit EC2 AMI wont
>> stop "initializing"
>>
>> Did "yast2-firstboot" hack is still needed ?
>>
>> Cheers
>
>

[dmayer]

I found some issues with our internal timeouts and prepared a patch that should make it to the site tomorrow. The problem has nothing to do with architectures or installed packages or services. Apparently, EC2 just slowed down a bit during the last weeks and therefore our upload process times out before the snapshot creation is completed. Check back tomorrow and retry. It should be fixed by then.

Dominik

[Björn Geuken]

Hi guys,

we are aware of the problem and Dominik is already working on that
issue. He also replied in the forum, but the mail was not send to the
mailing list. So in case that you missed it, here is his message:

 > I found some issues with our internal timeouts and prepared a patch
that should make it to the site tomorrow. The problem has nothing to do with
 > architectures or installed packages or services. Apparently, EC2 just
slowed down a bit during the last weeks and therefore our upload process
 > times out before the snapshot creation is completed. Check back
tomorrow and retry. It should be fixed by then.
 >
 > Dominik

Cheers,
Björn

[Raphael Lydia Bertoche]

Good to hear that.
But why in hell would this get fixed by removing systemd and installing sysvinit? I don't think my issue is the same.
I'll try again tomorrow anyway.

Thanks
Raphael

2012/4/3 Björn Geuken <[hidden email]>

On 04/03/2012 04:08 PM, Raphael Lydia Bertoche wrote:

No, I had this problem with x86_64.

On 3 April 2012 06:27, Henri Gomez <[hidden email]> wrote:

Did problem appears only for x86 (32bits) OpenSuse 12.1 appliance ?

I did a JeOS 12.1 64bits and didn't get such problem

2012/4/3 Raphael Lydia Bertoche <[hidden email]>:

> I had the same problem. Got it solved (in an ugly way) using sysvinit
> instead of systemd.
> http://susestudio.com/a/MPE71Z/aws-opensuse-121-with-sysvinit-x86
>
> Raphael
> <a href="tel:%2821%29%209162%205605" value="[phone]" target="_blank">(21) 9162 5605
> <a href="tel:%2821%29%203527%202253" value="[phone]" target="_blank">(21) 3527 2253
>
>
>
> On 2 April 2012 19:18, Henri Gomez <[hidden email]> wrote:
>>
>> Hi to all,
>>
>> I tried many time today to upload to EC2 a very basic OpenSuse 12.1
>> (JeOS) 32 bits to my AWS Account.
>>
>> AWS create SNAPSHOT but AMI can't be created and Studio Fail in Timeout.
>>
>> I see a thread with a similar problem "My SUSEStudio buit EC2 AMI wont
>> stop "initializing"
>>
>> Did "yast2-firstboot" hack is still needed ?
>>
>> Cheers
>
>

Hi guys,

we are aware of the problem and Dominik is already working on that issue. He also replied in the forum, but the mail was not send to the mailing list. So in case that you missed it, here is his message:

> I found some issues with our internal timeouts and prepared a patch that should make it to the site tomorrow. The problem has nothing to do with
> architectures or installed packages or services. Apparently, EC2 just slowed down a bit during the last weeks and therefore our upload process
> times out before the snapshot creation is completed. Check back tomorrow and retry. It should be fixed by then.
>
> Dominik

Cheers,
Björn

[hgomez]

Good news.

Could you send a notice here when EC2 fix has been applied ?

Cheers

2012/4/3 Raphael Lydia Bertoche <[hidden email]>:

> Good to hear that.
> But why in hell would this get fixed by removing systemd and installing
> sysvinit? I don't think my issue is the same.
> I'll try again tomorrow anyway.
>
> Thanks
> Raphael
>
>
> 2012/4/3 Björn Geuken <[hidden email]>
>>
>> On 04/03/2012 04:08 PM, Raphael Lydia Bertoche wrote:
>>
>> No, I had this problem with x86_64.
>>
>>
>> On 3 April 2012 06:27, Henri Gomez <[hidden email]> wrote:
>>>
>>> Did problem appears only for x86 (32bits) OpenSuse 12.1 appliance ?
>>>
>>> I did a JeOS 12.1 64bits and didn't get such problem
>>>
>>> 2012/4/3 Raphael Lydia Bertoche <[hidden email]>:
>>> > I had the same problem. Got it solved (in an ugly way) using sysvinit
>>> > instead of systemd.
>>> > http://susestudio.com/a/MPE71Z/aws-opensuse-121-with-sysvinit-x86
>>> >
>>> > Raphael
>>> > (21) 9162 5605
>>> > (21) 3527 2253
>>> >
>>> >
>>> >
>>> > On 2 April 2012 19:18, Henri Gomez <[hidden email]> wrote:
>>> >>
>>> >> Hi to all,
>>> >>
>>> >> I tried many time today to upload to EC2 a very basic OpenSuse 12.1
>>> >> (JeOS) 32 bits to my AWS Account.
>>> >>
>>> >> AWS create SNAPSHOT but AMI can't be created and Studio Fail in
>>> >> Timeout.
>>> >>
>>> >> I see a thread with a similar problem "My SUSEStudio buit EC2 AMI wont
>>> >> stop "initializing"
>>> >>
>>> >> Did "yast2-firstboot" hack is still needed ?
>>> >>
>>> >> Cheers
>>> >
>>> >
>>
>>
>> Hi guys,
>>
>> we are aware of the problem and Dominik is already working on that issue.
>> He also replied in the forum, but the mail was not send to the mailing list.
>> So in case that you missed it, here is his message:
>>
>> > I found some issues with our internal timeouts and prepared a patch that
>> > should make it to the site tomorrow. The problem has nothing to do with
>> > architectures or installed packages or services. Apparently, EC2 just
>> > slowed down a bit during the last weeks and therefore our upload process
>> > times out before the snapshot creation is completed. Check back tomorrow
>> > and retry. It should be fixed by then.
>> >
>> > Dominik
>>
>> Cheers,
>> Björn
>
>

[Björn Geuken]

On 04/04/2012 10:23 AM, Henri Gomez wrote:
> Good news.
>
> Could you send a notice here when EC2 fix has been applied ?
>
> Cheers
The fix has been applied 30 minutes ago. Please try it out and let us
know if you still get those timeouts.

Cheers
Björn

[hgomez]

> The fix has been applied 30 minutes ago. Please try it out and let us know
> if you still get those timeouts.

Fix seems to works. Just upload with success an OpenSUSE 12.1 32bits
in JeOS mode.

Thanks team !

[Raphael Lydia Bertoche]

My appliance is still not working. Stops at 1/2 status checks passed,
not pinging nor logging through ssh.
I have a working version with sysvinit, sysvinit-init and
sysvinit-tools, but after removing them and installing systemd and
systemd-sysvinit it gets unreachable.

Got any clues?

Log from AWS, from 3 lines above first error:

[    0.315040] netfront: Initialising virtual ethernet driver.

Creating device nodes with udev
[    0.428344] udevd[63]: starting version 173

udevd[86]: failed to execute
'/etc/sysconfig/network/scripts/ifup-sysctl'
'/etc/sysconfig/network/scripts/ifup-sysctl lo -o hotplug': No such
file or directory


udevd[89]: failed to execute
'/etc/sysconfig/network/scripts/ifup-sysctl'
'/etc/sysconfig/network/scripts/ifup-sysctl eth0 -o hotplug': No such
file or directory


mount: devpts already mounted or /dev/pts busy
mount: according to mtab, devpts is already mounted on /dev/pts

Boot logging started on /dev/xvc0(/dev/console) at Thu Apr  5 19:06:25 2012
Waiting for device /dev/sda1 to appear:  ok
fsck from util-linux 2.20.1
[/sbin/fsck.ext2 (1) -- /] fsck.ext2 -a /dev/sda1
/dev/sda1: clean, 80544/655360 files, 566286/2621439 blocks
fsck succeeded. Mounting root device read-write.
Mounting root /dev/sda1
mount -o rw -t ext2 /dev/sda1 /root
[    4.323692] EXT4-fs (sda1): mounting ext2 file system using the
ext4 subsystem

[    4.327406] EXT4-fs (sda1): mounted filesystem with ordered data
mode. Opts: (null)

[    5.055916] EXT4-fs (sda1): re-mounted. Opts: acl,user_xattr

[    5.880638] systemd[1]: systemd 37 running in system mode. (+PAM
+LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; suse)


Welcome to
    [0;32mopenSUSE 12.1 (Asparagus) (x86_64)
    [0m!

[    7.082813] systemd[1]: Set hostname to <linux-gwyt>.

Started Replay Read-Ahead Data                                          [
    [1;32m  OK
    [0m]
Starting Collect Read-Ahead Data...
Starting Runtime Directory...
Starting Media Directory...
Starting Lock Directory...
Starting POSIX Message Queue File System...
Started Huge Pages File System                                          [
    [1;32m  OK
    [0m]
Starting Debug File System...
Starting Security File System...
Started Start bootsplash                                                [
    [1;32m  OK
    [0m]
Starting udev Coldplug all Devices...
Starting udev Kernel Device Manager...
Starting Syslog Kernel Log Buffer Bridge...
Started Syslog Kernel Log Buffer Bridge                                 [
    [1;32m  OK
    [0m]
Starting STDOUT Syslog Bridge...
Started STDOUT Syslog Bridge                                            [
    [1;32m  OK
    [0m]
Started udev Kernel Device Manager                                      [
    [1;32m  OK
    [0m]
[    9.192433] udevd[199]: starting version 173

Started Lock Directory                                                  [
    [1;32m  OK
    [0m]
Started Debug File System                                               [
    [1;32m  OK
    [0m]
Started Runtime Directory                                               [
    [1;32m  OK
    [0m]
Started Security File System                                            [
    [1;32m  OK
    [0m]
Started POSIX Message Queue File System                                 [
    [1;32m  OK
    [0m]
Started Media Directory                                                 [
    [1;32m  OK
    [0m]
Started udev Coldplug all Devices                                       [
    [1;32m  OK
    [0m]
Started Collect Read-Ahead Data                                         [
    [1;32m  OK
    [0m]
Starting Remount API VFS...
Starting Setup Virtual Console...
Started File System Check on Root Device                                [
    [1;32m  OK
    [0m]
Starting LSB: setup hostname and yp...
Starting Remount Root FS...
Started Set Up Additional Binary Formats                                [
    [1;32m  OK
    [0m]
Starting Load Kernel Modules...
Started Remount API VFS                                                 [
    [1;32m  OK
    [0m]
Started Load Kernel Modules                                             [
    [1;32m  OK
    [0m]
Starting Apply Kernel Variables...
Started Configuration File System                                       [
    [1;32m  OK
    [0m]
Started FUSE Control File System                                        [
    [1;32m  OK
    [0m]
Started Apply Kernel Variables                                          [
    [1;32m  OK
    [0m]
[    9.793809] EXT4-fs (sda1): re-mounted. Opts: acl,user_xattr

Started Remount Root FS                                                 [
    [1;32m  OK
    [0m]
[    9.978064] boot.localnet[252]: Using boot-specified hostname 'linux-gwyt'

boot.localnet[252]: Using boot-specified hostname 'linux-gwyt'
boot.localnet[252]: Setting up hostname 'linux-gwyt'..done
[    9.981038] boot.localnet[252]: Setting up hostname 'linux-gwyt'..done

[    9.990032] ifup[282]: Service network not started and mode 'auto'
-> skipping

boot.localnet[252]: Setting up loopback interface RTNETLINK answers: File exists
[    9.998034] boot.localnet[252]: Setting up loopback interface
RTNETLINK answers: File exists

boot.localnet[252]: ..done
[   10.006120] boot.localnet[252]: ..done

Started LSB: setup hostname and yp                                      [
    [1;32m  OK
    [0m]
Started Setup Virtual Console                                           [
    [1;32m  OK
    [0m]
[   98.983532] systemd[1]: Job dev-sdb.device/start timed out.

Dependency failed. Aborted start of /mnt                                [
    [1;31m ABORT
    [0m]
[   98.983650] systemd[1]: Job remote-fs-pre.target/start failed with
result 'dependency'.

[   98.983660] systemd[1]: Job local-fs.target/start failed with
result 'dependency'.

[   98.983666] systemd[1]: Triggering OnFailure= dependencies of
local-fs.target.

[   98.984334] systemd[1]: Job mnt.mount/start failed with result 'dependency'.

[   98.984344] systemd[1]: Job dev-sdb.device/start failed with result
'timeout'.

[   99.008606] systemd[293]: Failed at step EXEC spawning
/bin/plymouth: No such file or directory

Welcome to emergency mode. Use "systemctl default" or ^D to activate
default mode.
Give root password for login: [   99.034676] systemd[1]: Startup
finished in 7s 83ms 717us (kernel) + 1min 31s 950ms 641us (userspace)
= 1min 39s 34ms 358us.