Restarting openQA-gru

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Restarting openQA-gru

Lakshmipathi.G
Hi -

I'm new to openQA and installed it Tumbleweed (Snapshot20180114). It
worked well without any issue
for the first time. After reboot the machine, openqa-gru fails to
start.  how do i fix this resolve this
problem? Please let me know if you need more details or logs. thanks.

---
laks@qabot:~> sudo systemctl status openqa-gru
● openqa-gru.service - The openQA gru daemon
   Loaded: loaded (/usr/lib/systemd/system/openqa-gru.service;
disabled; vendor preset: disabled)
   Active: active (running) since Sun 2018-01-21 08:08:06 IST; 5s ago
 Main PID: 2718 (openqa)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/openqa-gru.service
           └─2718 /usr/bin/perl /usr/share/openqa/script/openqa gru -m
production run

Jan 21 08:08:06 qabot systemd[1]: Started The openQA gru daemon.
laks@qabot:~> sudo systemctl status openqa-gru
● openqa-gru.service - The openQA gru daemon
   Loaded: loaded (/usr/lib/systemd/system/openqa-gru.service;
disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sun 2018-01-21 08:08:12 IST; 3s ago
  Process: 2718 ExecStart=/usr/share/openqa/script/openqa gru -m
production run (code=exited, status=13)
 Main PID: 2718 (code=exited, status=13)

Jan 21 08:08:12 qabot openqa[2718]: Compilation failed in require at
/usr/share/openqa/script/../lib/OpenQA/Schema/Result/Assets.pm line
25.
Jan 21 08:08:12 qabot openqa[2718]: BEGIN failed--compilation aborted
at /usr/share/openqa/script/../lib/OpenQA/Schema/Result/Assets.pm line
25.
Jan 21 08:08:12 qabot openqa[2718]: Compilation failed in require at
/usr/lib/perl5/vendor_perl/5.26.1/Class/C3/Componentised.pm line 150.
at /usr/lib
Jan 21 08:08:12 qabot openqa[2718]: Compilation failed in require at
/usr/share/openqa/script/../lib/OpenQA/WebAPI.pm line 24.
Jan 21 08:08:12 qabot openqa[2718]: BEGIN failed--compilation aborted
at /usr/share/openqa/script/../lib/OpenQA/WebAPI.pm line 24.
Jan 21 08:08:12 qabot openqa[2718]: Compilation failed in require at
/usr/share/openqa/script/openqa line 32.
Jan 21 08:08:12 qabot openqa[2718]: BEGIN failed--compilation aborted
at /usr/share/openqa/script/openqa line 32.
Jan 21 08:08:12 qabot systemd[1]: openqa-gru.service: Main process
exited, code=exited, status=13/n/a
Jan 21 08:08:12 qabot systemd[1]: openqa-gru.service: Unit entered failed state.
Jan 21 08:08:12 qabot systemd[1]: openqa-gru.service: Failed with
result 'exit-code'.
---
While running openqa-gru directly and using strace

sudo /usr/share/openqa/script/openqa gru -m production run
Uncaught exception from user code:
    {UNKNOWN}: Permission denied
    Compilation failed in require at
/usr/share/openqa/script/../lib/OpenQA/Schema/Result/Assets.pm line
25.
    BEGIN failed--compilation aborted at
/usr/share/openqa/script/../lib/OpenQA/Schema/Result/Assets.pm line
25.
    Compilation failed in require at
/usr/lib/perl5/vendor_perl/5.26.1/Class/C3/Componentised.pm line 150.
at /usr/lib/perl5/vendor_perl/5.26.1/Class/C3/Componentised.pm line
155
    Compilation failed in require at
/usr/share/openqa/script/../lib/OpenQA/WebAPI.pm line 24.
    BEGIN failed--compilation aborted at
/usr/share/openqa/script/../lib/OpenQA/WebAPI.pm line 24.
    Compilation failed in require at /usr/share/openqa/script/openqa line 32.
    BEGIN failed--compilation aborted at
/usr/share/openqa/script/openqa line 32.

openat(AT_FDCWD, "/usr/bin/unzip", O_RDONLY) = -1 EACCES (Permission denied)
lseek(5, 935, SEEK_SET)                 = 935
lseek(5, 0, SEEK_CUR)                   = 935
close(5)                                = 0
lseek(4, 848, SEEK_SET)                 = 848
lseek(4, 0, SEEK_CUR)                   = 848
close(4)                                = 0
write(2, "Uncaught exception from user cod"..., 799Uncaught exception
from user code:
    {UNKNOWN}: Permission denied
    Compilation failed in require at
/usr/share/openqa/script/../lib/OpenQA/Schema/Result/Assets.pm line
25.
    BEGIN failed--compilation aborted at
/usr/share/openqa/script/../lib/OpenQA/Schema/Result/Assets.pm line
25.
    Compilation failed in require at
/usr/lib/perl5/vendor_perl/5.26.1/Class/C3/Componentised.pm line 150.
at /usr/lib/perl5/vendor_perl/5.26.1/Class/C3/Componentised.pm line
155
    Compilation failed in require at
/usr/share/openqa/script/../lib/OpenQA/WebAPI.pm line 24.
    BEGIN failed--compilation aborted at
/usr/share/openqa/script/../lib/OpenQA/WebAPI.pm line 24.
    Compilation failed in require at /usr/share/openqa/script/openqa line 32.
    BEGIN failed--compilation aborted at
/usr/share/openqa/script/openqa line 32.
) = 799

$ ls -l /usr/bin/unzip
lrwxrwxrwx 1 root root 23 Jan 11 12:17 /usr/bin/unzip -> /etc/alternatives/unzip
$ readlink -f /usr/bin/unzip
/usr/bin/unzip-plain
$ ls -l /usr/bin/unzip-plain
-rwxr-xr-x 1 root root 166760 Jan 11 12:17 /usr/bin/unzip-plain


----
Cheers,
Lakshmipathi.G
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Restarting openQA-gru

Oliver Kurz-2


Am 21. Januar 2018 04:05:53 MEZ schrieb "Lakshmipathi.G" <[hidden email]>:

>Hi -
>
>I'm new to openQA and installed it Tumbleweed (Snapshot20180114). It
>worked well without any issue
>for the first time. After reboot the machine, openqa-gru fails to
>start.  how do i fix this resolve this
>problem? Please let me know if you need more details or logs. thanks.
>
>---
>laks@qabot:~> sudo systemctl status openqa-gru
>● openqa-gru.service - The openQA gru daemon
>   Loaded: loaded (/usr/lib/systemd/system/openqa-gru.service;
>disabled; vendor preset: disabled)
>   Active: active (running) since Sun 2018-01-21 08:08:06 IST; 5s ago
> Main PID: 2718 (openqa)
>    Tasks: 1 (limit: 4915)
>   CGroup: /system.slice/openqa-gru.service
>           └─2718 /usr/bin/perl /usr/share/openqa/script/openqa gru -m
>production run
>
>Jan 21 08:08:06 qabot systemd[1]: Started The openQA gru daemon.
>laks@qabot:~> sudo systemctl status openqa-gru
>● openqa-gru.service - The openQA gru daemon
>   Loaded: loaded (/usr/lib/systemd/system/openqa-gru.service;
>disabled; vendor preset: disabled)
>Active: failed (Result: exit-code) since Sun 2018-01-21 08:08:12 IST;
>3s ago
>  Process: 2718 ExecStart=/usr/share/openqa/script/openqa gru -m
>production run (code=exited, status=13)
> Main PID: 2718 (code=exited, status=13)
>
>Jan 21 08:08:12 qabot openqa[2718]: Compilation failed in require at
>/usr/share/openqa/script/../lib/OpenQA/Schema/Result/Assets.pm line
>25.
>Jan 21 08:08:12 qabot openqa[2718]: BEGIN failed--compilation aborted
>at /usr/share/openqa/script/../lib/OpenQA/Schema/Result/Assets.pm line
>25.
>Jan 21 08:08:12 qabot openqa[2718]: Compilation failed in require at
>/usr/lib/perl5/vendor_perl/5.26.1/Class/C3/Componentised.pm line 150.
>at /usr/lib
>Jan 21 08:08:12 qabot openqa[2718]: Compilation failed in require at
>/usr/share/openqa/script/../lib/OpenQA/WebAPI.pm line 24.
>Jan 21 08:08:12 qabot openqa[2718]: BEGIN failed--compilation aborted
>at /usr/share/openqa/script/../lib/OpenQA/WebAPI.pm line 24.
>Jan 21 08:08:12 qabot openqa[2718]: Compilation failed in require at
>/usr/share/openqa/script/openqa line 32.
>Jan 21 08:08:12 qabot openqa[2718]: BEGIN failed--compilation aborted
>at /usr/share/openqa/script/openqa line 32.
>Jan 21 08:08:12 qabot systemd[1]: openqa-gru.service: Main process
>exited, code=exited, status=13/n/a
>Jan 21 08:08:12 qabot systemd[1]: openqa-gru.service: Unit entered
>failed state.
>Jan 21 08:08:12 qabot systemd[1]: openqa-gru.service: Failed with
>result 'exit-code'.
>---
>While running openqa-gru directly and using strace
>
>sudo /usr/share/openqa/script/openqa gru -m production run
>Uncaught exception from user code:
>    {UNKNOWN}: Permission denied
>    Compilation failed in require at
>/usr/share/openqa/script/../lib/OpenQA/Schema/Result/Assets.pm line
>25.
>    BEGIN failed--compilation aborted at
>/usr/share/openqa/script/../lib/OpenQA/Schema/Result/Assets.pm line
>25.
>    Compilation failed in require at
>/usr/lib/perl5/vendor_perl/5.26.1/Class/C3/Componentised.pm line 150.
>at /usr/lib/perl5/vendor_perl/5.26.1/Class/C3/Componentised.pm line
>155
>    Compilation failed in require at
>/usr/share/openqa/script/../lib/OpenQA/WebAPI.pm line 24.
>    BEGIN failed--compilation aborted at
>/usr/share/openqa/script/../lib/OpenQA/WebAPI.pm line 24.
>Compilation failed in require at /usr/share/openqa/script/openqa line
>32.
>    BEGIN failed--compilation aborted at
>/usr/share/openqa/script/openqa line 32.
>
>openat(AT_FDCWD, "/usr/bin/unzip", O_RDONLY) = -1 EACCES (Permission
>denied)

Hm, sounds to me like an apparmor related problem. Try to disable the apparmor service, make sure all openqa services start fine, then start apparmor again.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Restarting openQA-gru

Lakshmipathi.G
Thanks for the suggestions Oliver. Unfortunately issue still persists.
Here is the commands I followed:

systemctl start apache2
systemctl start postgresql
systemctl stop apparmor
and
systemctl start openqa-gru.

short screencast:  https://asciinema.org/a/jsweHBl0rqYo6WQegS8g7Jg5x

More log from journalctl while starting openqa-gru:

Jan 21 15:22:09 qabot gnome-terminal-[2688]: Allocating size to
GtkScrollbar 0x562012862460 without calling
gtk_widget_get_preferred_width/height(). How does the code know the
size to allocate?
Jan 21 15:22:18 qabot sudo[5962]:     laks : TTY=pts/1 ;
PWD=/home/laks ; USER=root ; COMMAND=/usr/bin/systemctl restart
openqa-gru
Jan 21 15:22:18 qabot sudo[5962]: pam_systemd(sudo:session): Cannot
create session: Already occupied by a session
Jan 21 15:22:18 qabot sudo[5962]: pam_unix(sudo:session): session
opened for user root by (uid=0)
Jan 21 15:22:18 qabot systemd[1]: Starting Setup local PostgreSQL
database for openQA...
Jan 21 15:22:18 qabot createuser[5965]: createuser: creation of new
role failed: ERROR:  role "geekotest" already exists
Jan 21 15:22:19 qabot createdb[5967]: createdb: database creation
failed: ERROR:  database "openqa" already exists
Jan 21 15:22:19 qabot systemd[1]: Started Setup local PostgreSQL
database for openQA.
Jan 21 15:22:19 qabot systemd[1]: Started The openQA gru daemon.
Jan 21 15:22:19 qabot sudo[5962]: pam_unix(sudo:session): session
closed for user root
Jan 21 15:22:21 qabot openqa[5969]: Uncaught exception from user code:
Jan 21 15:22:21 qabot openqa[5969]:         {UNKNOWN}: {UNKNOWN}:
Permission denied
Jan 21 15:22:21 qabot openqa[5969]:         Compilation failed in
require at /usr/share/openqa/script/../lib/OpenQA/Schema/Result/Assets.pm
line 25.
Jan 21 15:22:21 qabot openqa[5969]:         BEGIN failed--compilation
aborted at /usr/share/openqa/script/../lib/OpenQA/Schema/Result/Assets.pm
line 25.
Jan 21 15:22:21 qabot openqa[5969]:         Compilation failed in
require at /usr/lib/perl5/vendor_perl/5.26.1/Class/C3/Componentised.pm
line 150. at /usr/lib/perl5/vendor_perl/5.26.1/Class/C3/Componentised.pm
line 155
Jan 21 15:22:21 qabot openqa[5969]:         Compilation failed in
require at /usr/share/openqa/script/../lib/OpenQA/WebAPI.pm line 24.
Jan 21 15:22:21 qabot openqa[5969]:         BEGIN failed--compilation
aborted at /usr/share/openqa/script/../lib/OpenQA/WebAPI.pm line 24.
Jan 21 15:22:21 qabot openqa[5969]:         Compilation failed in
require at /usr/share/openqa/script/openqa line 32.
Jan 21 15:22:21 qabot openqa[5969]:         BEGIN failed--compilation
aborted at /usr/share/openqa/script/openqa line 32.
Jan 21 15:22:21 qabot systemd[1]: openqa-gru.service: Main process
exited, code=exited, status=13/n/a
Jan 21 15:22:21 qabot systemd[1]: openqa-gru.service: Unit entered failed state.
Jan 21 15:22:21 qabot systemd[1]: openqa-gru.service: Failed with
result 'exit-code'.

thanks for the help.

----
Cheers,
Lakshmipathi.G
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Restarting openQA-gru

Michael Ströder
Lakshmipathi.G wrote:
> Thanks for the suggestions Oliver. Unfortunately issue still persists.
> Here is the commands I followed:
>
> systemctl start apache2
> systemctl start postgresql
> systemctl stop apparmor
> and
> systemctl start openqa-gru.

IIRC systemctl stop apparmor does not work anymore as expected (see
Christian's message below).

Ciao, Michael.

-------- Forwarded Message --------
Subject: AppArmor changes (was: [opensuse-factory] New Tumbleweed
snapshot 20180101 released!)
Date: Wed, 03 Jan 2018 14:11:44 +0100
From: Christian Boltz <[hidden email]>
To: [hidden email]

Hello,

Am Mittwoch, 3. Januar 2018, 12:45:44 CET schrieb Dominique Leuenberger:
> ==== apparmor ====
> Version update (2.11.1 -> 2.12)

I should probably highlight this change:

> - add aa-teardown (new script to unload all profiles)
> - make ExecStop in apparmor.service a no-op (workaround for a systemd
>   restriction, see boo#996520 and boo#853019 for details)

The short version is:
"rcapparmor stop" and "systemctl stop apparmor" won't do anything now
because of the way how systemd implements "restart" [insert systemd rant
here].

If you really want to unload your AppArmor profiles, run "aa-teardown".
But - who would do that? ;-)  [1]

The longer version is on
https://blog.cboltz.de/archives/77-AppArmor-2.12-The-Grinch-is-confined!.html
;-)


Regards,

Christian Boltz

[1] aa-complain /etc/apparmor.d/$whatever is a much better choice
because it logs what would be denied and allows you to update the
    profile and/or to open a bugreport with useful logs


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Restarting openQA-gru

Lakshmipathi.G
> IIRC systemctl stop apparmor does not work anymore as expected (see
> Christian's message below).

Spot on! openqa-gru got re-started after using 'sudo aa-teardown' :-)

Thanks Michael and Oliver!

----
Cheers,
Lakshmipathi.G
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Restarting openQA-gru

Michael Ströder
Lakshmipathi.G wrote:
>> IIRC systemctl stop apparmor does not work anymore as expected (see
>> Christian's message below).
>
> Spot on! openqa-gru got re-started after using 'sudo aa-teardown' :-)
>
> Thanks Michael and Oliver!

Kudos to Christian Boltz for his hint about aa-teardown.

Ciao, Michael.


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Restarting openQA-gru

Christian Boltz-5
In reply to this post by Lakshmipathi.G
Hello,

Am Sonntag, 21. Januar 2018, 15:39:11 CET schrieb Lakshmipathi.G:
> > IIRC systemctl stop apparmor does not work anymore as expected (see
> > Christian's message below).
>
> Spot on! openqa-gru got re-started after using 'sudo aa-teardown' :-)

And now, please check your /var/log/audit/audit.log or run aa-logprof to
find out what needs to be added to the profile, and open a bugreport ;-)

BTW: Instead of unloading all profiles with aa-teardown, it's usually
better to switch the profile to complain (learning) mode with
    aa-complain /etc/apparmor.d/usr.bin.openqa-gru
    (adjust the profile filename, the above is only a guess!)
because that gives you a more complete log of things that need to be
added to the profile.


Regards,

Christian Boltz
--
I believe the technical term is "Oops!"



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Restarting openQA-gru

Lakshmipathi.G
>
> And now, please check your /var/log/audit/audit.log or run aa-logprof to
> find out what needs to be added to the profile, and open a bugreport ;-)
>

Sure, I'll explore apparmor as you have suggested and open a bugreport
soon :-)  Thanks.

----
Cheers,
Lakshmipathi.G
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]