[Spacewalk-list] ipmievd.service failed

2019-02-15 Thread Ron Skantz
Spacewalk 2.9 on Centos 7

Any ideas on how I can get this service to start correctly?

Thanks in advance for any advice or help you can provide!

Here are some details:

root@aws-space1:~ $ systemctl status ipmievd.service
● ipmievd.service - Ipmievd Daemon
   Loaded: loaded (/usr/lib/systemd/system/ipmievd.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Fri 2019-02-15 13:57:37 EST; 9s ago
  Process: 3694 ExecStart=/usr/sbin/ipmievd $IPMIEVD_OPTIONS (code=exited, 
status=1/FAILURE)

Feb 15 13:57:37 aws-space1 ipmievd[3694]: Could not open device at /dev/ipmi0 
or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
Feb 15 13:57:37 aws-space1 systemd[1]: ipmievd.service: control process exited, 
code=exited status=1
Feb 15 13:57:37 aws-space1 systemd[1]: Failed to start Ipmievd Daemon.
Feb 15 13:57:37 aws-space1 systemd[1]: Unit ipmievd.service entered failed 
state.
Feb 15 13:57:37 aws-space1 systemd[1]: ipmievd.service failed.
root@aws-space1:~ $



It seems like a lot of spacewalk services rely on this to work:

root@aws-space1:~ $ repoquery --whatrequires --recursive ipmitool 
--disablerepo=epel
bmc-snmp-proxy-0:1.8.18-7.el7.noarch
cobbler-loaders-0:1.0.3-2.el7.noarch
cobbler-web-0:2.0.11-85.el7.noarch
cobbler2-0:2.0.11-85.el7.noarch
cobbler20-0:2.0.11-85.el7.noarch
exchange-bmc-os-info-0:1.8.18-7.el7.noarch
fence-agents-all-0:4.2.1-11.el7.x86_64
fence-agents-all-0:4.2.1-11.el7_6.1.x86_64
fence-agents-all-0:4.2.1-11.el7_6.7.x86_64
fence-agents-ipmilan-0:4.2.1-11.el7.x86_64
fence-agents-ipmilan-0:4.2.1-11.el7_6.1.x86_64
fence-agents-ipmilan-0:4.2.1-11.el7_6.7.x86_64
osa-dispatcher-selinux-0:5.11.107-1.el7.noarch
spacewalk-backend-tools-0:2.9.33-1.el7.noarch
spacewalk-backend-tools-0:2.9.34-1.el7.noarch
spacewalk-common-0:2.8.2-1.el7.noarch
spacewalk-java-0:2.9.30-1.el7.noarch
spacewalk-oracle-0:2.8.2-1.el7.noarch
spacewalk-postgresql-0:2.8.2-1.el7.noarch
spacewalk-schema-0:2.9.11-1.el7.noarch
spacewalk-selinux-0:2.9.6-1.el7.noarch
spacewalk-setup-0:2.9.3-1.el7.noarch
spacewalk-taskomatic-0:2.9.30-1.el7.noarch
spacewalk-utils-0:2.9.9-1.el7.noarch
root@aws-space1:~ $

Thanks,

Ron


PRIVILEGED AND CONFIDENTIAL: This electronic message and any attachments are 
confidential property of the sender. The information is intended only for the 
use of the person to whom it was addressed. Any other interception, copying, 
accessing, or disclosure of this message is prohibited. The sender takes no 
responsibility for any unauthorized reliance on this message. If you have 
received this message in error, please immediately notify the sender and purge 
the message you received. Do not forward this message without permission.


___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Sequences going wrong

2019-02-15 Thread Robert Paschedag
Am 15. Februar 2019 09:28:26 MEZ schrieb Thomas Schweikle 
:
>On 14.02.2019 12:09, p.cookson-mhdz94l+r7k1qrn1bg8...@public.gmane.org
>wrote:
>> Hi Thomas
>> 
>> The "Internal Server Error" appears to be a really generic and
>un-helpful message that comes out of Spacewalk in all sorts of
>scenario's! I haven't experienced your particular problem but, in the
>past, I've been advised to look at " /var/log/tomcat/catalina.out" to
>try and get a better idea of what the issue is. Don't know if this will
>help on this occasion?
>
>No, this was not helpful in this occasion. I'd need some way to make
>spacewalk deliver what error was created, by taking logs from
>/var/log/tomcat/catalina.out,
>/var/lib/pgsql/11/data/log/postgres-*.log.
>
>It would be really helpful spacewalk pushing the error logs to the web
>interface for debugging such cases!
>
>> 
>> Regards
>> Phil
>> 
>> -Original Message-
>> From: spacewalk-list-bounces-h+wxahxf7alqt0dzr+a...@public.gmane.org
> On
>Behalf Of tschweikle-re5jqeeqqe8avxtiumw...@public.gmane.org
>> Sent: 14 February 2019 10:31
>> To: spacewalk
>
>> Subject: [Spacewalk-list] Sequences going wrong
>> 
>> Hi!
>> 
>> We're having a lot of troubble with spacewalk loosing sequences, or
>> better: loosing sync within sequences. As spacewalk runs all looks ok
>for some time. then you may get "Internal server error" at a variety of
>places. Mostly it starts showing up in "Schedule -> Actions" click on
>one of the numbers behind in columns Finished, Failed, Pending.
>> Instead of showing me details on where the action hav finished,
>failed or is pending I am prompted with "Internal server error".
>> 
>> Looking into the sql-logs I can find sequences out of sync. Fixing
>these manually makes it work again -- for some time. I do not have any
>idea why these sequences starting to get out of sync. Any idea? Bug?
>> 
>> Spacewalk 2.9
>> OS: CentOS 7
>> 
>> --
>> Thomas
>> 
>> ___
>> Spacewalk-list mailing list
>> spacewalk-list-h+wxahxf7alqt0dzr+a...@public.gmane.org
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>> 

Well... You can look into the stack traces at which file (and line) the error 
occurred. Clone the spacewalk git repo, checkout your version "branch" and look 
at the code.

Robert
-- 
sent from my mobile device

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list


Re: [Spacewalk-list] Sequences going wrong

2019-02-15 Thread Thomas Schweikle
On 14.02.2019 12:09, p.cookson-mhdz94l+r7k1qrn1bg8...@public.gmane.org
wrote:
> Hi Thomas
> 
> The "Internal Server Error" appears to be a really generic and un-helpful 
> message that comes out of Spacewalk in all sorts of scenario's! I haven't 
> experienced your particular problem but, in the past, I've been advised to 
> look at " /var/log/tomcat/catalina.out" to try and get a better idea of what 
> the issue is. Don't know if this will help on this occasion?

No, this was not helpful in this occasion. I'd need some way to make
spacewalk deliver what error was created, by taking logs from
/var/log/tomcat/catalina.out, /var/lib/pgsql/11/data/log/postgres-*.log.

It would be really helpful spacewalk pushing the error logs to the web
interface for debugging such cases!

> 
> Regards
> Phil
> 
> -Original Message-
> From: spacewalk-list-bounces-h+wxahxf7alqt0dzr+a...@public.gmane.org 
>  On Behalf Of 
> tschweikle-re5jqeeqqe8avxtiumw...@public.gmane.org
> Sent: 14 February 2019 10:31
> To: spacewalk 
> Subject: [Spacewalk-list] Sequences going wrong
> 
> Hi!
> 
> We're having a lot of troubble with spacewalk loosing sequences, or
> better: loosing sync within sequences. As spacewalk runs all looks ok for 
> some time. then you may get "Internal server error" at a variety of places. 
> Mostly it starts showing up in "Schedule -> Actions" click on one of the 
> numbers behind in columns Finished, Failed, Pending.
> Instead of showing me details on where the action hav finished, failed or is 
> pending I am prompted with "Internal server error".
> 
> Looking into the sql-logs I can find sequences out of sync. Fixing these 
> manually makes it work again -- for some time. I do not have any idea why 
> these sequences starting to get out of sync. Any idea? Bug?
> 
> Spacewalk 2.9
> OS: CentOS 7
> 
> --
> Thomas
> 
> ___
> Spacewalk-list mailing list
> spacewalk-list-h+wxahxf7alqt0dzr+a...@public.gmane.org
> https://www.redhat.com/mailman/listinfo/spacewalk-list
> 


-- 
Thomas

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list