subject:"\[Spacewalk\-list\] Ongoing Jabberd issues on SW 2.9\/Centos7 servers"

Re: [Spacewalk-list] Ongoing Jabberd issues on SW 2.9/Centos7 Servers

2019-10-07 Thread Wilkinson, Matthew

I've been using Spacewalk since 2013 and I cannot recommend anything to fix 
jabber as much as I can switching to the postgresdb. Just do it. You'll thank 
yourself later.

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Paul-Andre Panon
Sent: Friday, October 04, 2019 12:29
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Ongoing Jabberd issues on SW 2.9/Centos7 Servers

[This is an external email. Be cautious with links, attachments and responses.]

**
On Fri, 4 Oct 2019 09:30:44 -0700, Larry Clegg  wrote:

>Hello Spacewalkers,

>I am continuing to have issues on all my Centos7/Spacewalk 2.9 servers
with Jabberd failing.  It is failing consistently on every server.  I have 
verified that all >the /etc/jabberd/*.xml files have the same FQDN and same 
passwords.  The /etc/pki/spacewalk/jabberd/server.pem includes the same FQDN.

>I just don't know where else to look and trouble-shoot.

There's been a bunch of posts about Jabberd being unreliable when working with 
a Berkeley db. See the second paragraph in this post 
https://urldefense.proofpoint.com/v2/url?u=https-3A__omg.dje.li_2017_03_configuring-2Dspacewalks-2Djabberd-2Dto-2Duse-2Da-2Dpostgre&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=mDx9E5vnCsYQA2XEtNnrzs8jVGrsaofB51I-HHITTeY&s=iaUEN0Sr0l95ZhHSZQk4pXXPEH0fxKUE128LYpk5R_o&e=
sql-backend/

 I had similar problems until I switched to use postgres. It looks from your 
extracts that you're using sqlite or BerkeleyDB

>[root@us3-inf-lu-s01 jabberd]# pwd
>/var/lib/jabberd
>[root@us3-inf-lu-s01 jabberd]# ls -lR
...
>./db:
>total 8096
>-rw-r--r-- 1 jabber jabber  131072 Oct  4 11:53 sqlite.db
>-rw-r--r-- 1 jabber jabber   32768 Oct  4 12:26 sqlite.db-shm
>-rw-r--r-- 1 jabber jabber 4103552 Oct  4 12:26 sqlite.db-wal
...

Therefore I would suggest that you follow the instructions in that link and 
migrate your jabber database to the same postgres server as your Spacewalk db. 
My jabberd problems went away when I did that.

Cheers,

Paul-Andre

-- 

Your privacy is important to us. That is why we have taken appropriate measures 
to ensure the data you provide to us is kept secure. To learn more about how we 
process your personal information, how we comply with applicable data 
protection laws, and care for the security and privacy of your personal data, 
please review our Privacy Policy 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.motorolasolutions.com_en-5Fus_about_privacy-2Dpolicy.html-23privacystatement&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=mDx9E5vnCsYQA2XEtNnrzs8jVGrsaofB51I-HHITTeY&s=Kx_K-zRIBSEuQbnAjxQXNIRVMpdsWArELNLhoB-S-RE&e=
 >. 
If you have any questions related to data protection and compliance with 
applicable laws, please contact us at our Security Operations Center at
1-302-444-9838 or mail us at: 

Attention: Privacy Compliance Program, P.O. 
Box 59263, Schaumburg, IL USA, 60159-0263

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

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

Re: [Spacewalk-list] Ongoing Jabberd issues on SW 2.9/Centos7 Servers

2019-10-04 Thread Paul-Andre Panon

On Fri, 4 Oct 2019 09:30:44 -0700, Larry Clegg  wrote:

>Hello Spacewalkers,

>I am continuing to have issues on all my Centos7/Spacewalk 2.9 servers
with Jabberd failing.  It is failing consistently on every server.  I have
verified that all >the /etc/jabberd/*.xml files have the same FQDN and
same passwords.  The /etc/pki/spacewalk/jabberd/server.pem includes the
same FQDN.

>I just don't know where else to look and trouble-shoot.

There's been a bunch of posts about Jabberd being unreliable when working
with a Berkeley db. See the second paragraph in this post
https://omg.dje.li/2017/03/configuring-spacewalks-jabberd-to-use-a-postgre
sql-backend/

 I had similar problems until I switched to use postgres. It looks from
your extracts that you're using sqlite or BerkeleyDB

>[root@us3-inf-lu-s01 jabberd]# pwd
>/var/lib/jabberd
>[root@us3-inf-lu-s01 jabberd]# ls -lR
...
>./db:
>total 8096
>-rw-r--r-- 1 jabber jabber  131072 Oct  4 11:53 sqlite.db
>-rw-r--r-- 1 jabber jabber   32768 Oct  4 12:26 sqlite.db-shm
>-rw-r--r-- 1 jabber jabber 4103552 Oct  4 12:26 sqlite.db-wal
...

Therefore I would suggest that you follow the instructions in that link
and migrate your jabber database to the same postgres server as your
Spacewalk db. My jabberd problems went away when I did that.

Cheers,

Paul-Andre

-- 

Your privacy is important to us. That is why we have taken appropriate 
measures to ensure the data you provide to us is kept secure. To learn more 
about how we process your personal information, how we comply with 
applicable data protection laws, and care for the security and privacy of 
your personal data, please review our Privacy Policy 
.

If you have any questions related to data protection and compliance with 
applicable laws, please contact us at our Security Operations Center at 
1-302-444-9838 or mail us at: 

Attention: Privacy Compliance Program, P.O. 
Box 59263, Schaumburg, IL USA, 60159-0263

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

Re: [Spacewalk-list] Ongoing Jabberd issues on SW 2.9/Centos7 servers

2019-10-04 Thread Robert Paschedag

So also nothing within /var/log/messages?

⁣sent from my mobile device


 Originale Nachricht 
Von: Larry Clegg 
Gesendet: Fri Oct 04 18:30:44 GMT+02:00 2019
An: spacewalk-list@redhat.com
Betreff: [Spacewalk-list] Ongoing Jabberd issues on SW 2.9/Centos7 servers

Hello Spacewalkers,

I am continuing to have issues on all my Centos7/Spacewalk 2.9 servers
with Jabberd failing.  It is failing consistently on every server.  I have
verified that all the /etc/jabberd/*.xml files have the same FQDN and same
passwords.  The /etc/pki/spacewalk/jabberd/server.pem includes the same
FQDN.

I just don’t know where else to look and trouble-shoot.

I cannot find any logs for jabberd either:

[root@us3-inf-lu-s01 jabberd]# pwd
/var/lib/jabberd
[root@us3-inf-lu-s01 jabberd]# ls -lR
.:
total 0
drwx-- 2 jabber jabber  65 Oct  4 11:53 db
drwx-- 2 jabber jabber   6 Jul  4  2017 log
drwx-- 2 jabber jabber 105 Sep 17 19:06 pid

./db:
total 8096
-rw-r--r-- 1 jabber jabber  131072 Oct  4 11:53 sqlite.db
-rw-r--r-- 1 jabber jabber   32768 Oct  4 12:26 sqlite.db-shm
-rw-r--r-- 1 jabber jabber 4103552 Oct  4 12:26 sqlite.db-wal

./log:
total 0

./pid:
total 16
-rw-r--r-- 1 jabber jabber 4 Oct  4 11:53 c2s.pid
-rw-r--r-- 1 jabber jabber 4 Oct  4 11:53 router.pid
-rw-r--r-- 1 jabber jabber 4 Oct  4 11:53 s2s.pid
-rw-r--r-- 1 jabber jabber 4 Oct  4 11:53
us3-inf-lu-s01.inf.us3.cloud.kyriba.com.pid
[root@us3-inf-lu-s01 jabberd]#

Environment:
Centos7 with kernel 3.10.0-1062.1.2.el7.x86_64

Spacewalk 2.9
[root@us3-inf-lu-s01 jabberd]# rpm -qa | grep jab
spacewalk-setup-jabberd-2.9.2-1.el7.noarch
jabberpy-0.5-0.27.el7.noarch
jabberd-2.6.1-1.el7.x86_64

[root@us3-inf-lu-s01 jabberd]# rpm -qa | grep java
spacewalk-java-config-2.9.31-1.el7.noarch
java-1.8.0-openjdk-1.8.0.222.b10-1.el7_7.x86_64
javamail-1.4.6-8.el7.noarch
spacewalk-java-lib-2.9.31-1.el7.noarch
java-1.8.0-openjdk-devel-1.8.0.222.b10-1.el7_7.x86_64
java-1.8.0-openjdk-headless-1.8.0.222.b10-1.el7_7.x86_64
javapackages-tools-3.4.1-11.el7.noarch
xz-java-1.3-3.el7.noarch
python-javapackages-3.4.1-11.el7.noarch
javassist-3.16.1-10.el7.noarch
maven-javadoc-plugin-2.10.4-1.sw.noarch
spacewalk-java-postgresql-2.9.31-1.el7.noarch
spacewalk-java-2.9.31-1.el7.noarch
tzdata-java-2019c-1.el7.noarch

[root@us3-inf-lu-s01 ~]# rpm -qa | grep space
spacewalk-base-minimal-config-2.9.4-1.el7.noarch
spacewalk-search-2.9.1-1.el7.noarch
spacewalk-setup-jabberd-2.9.2-1.el7.noarch
spacewalk-schema-2.9.11-1.el7.noarch
spacewalk-remote-utils-2.9.6-1.el7.noarch
spacewalk-backend-app-2.9.35-1.el7.noarch
spacewalk-java-config-2.9.31-1.el7.noarch
spacecmd-2.9.9-1.el7.noarch
spacewalk-dobby-2.9.4-1.el7.noarch
spacewalk-backend-server-2.9.35-1.el7.noarch
spacewalk-backend-iss-2.9.35-1.el7.noarch
perl-XML-NamespaceSupport-1.11-10.el7.noarch
spacewalk-java-lib-2.9.31-1.el7.noarch
python2-spacewalk-usix-2.9.1-1.el7.noarch
spacewalk-backend-config-files-common-2.9.35-1.el7.noarch
spacewalk-backend-libs-2.9.35-1.el7.noarch
spacewalk-backend-iss-export-2.9.35-1.el7.noarch
spacewalk-backend-package-push-server-2.9.35-1.el7.noarch
spacewalk-backend-sql-postgresql-2.9.35-1.el7.noarch
spacewalk-branding-2.9.2-1.el7.noarch
spacewalk-html-2.9.4-1.el7.noarch
spacewalk-certs-tools-2.9.2-1.el7.noarch
spacewalk-selinux-2.9.6-1.el7.noarch
spacewalk-utils-2.9.9-1.el7.noarch
spacewalk-base-minimal-2.9.4-1.el7.noarch
spacewalk-base-2.9.4-1.el7.noarch
spacewalk-repo-2.9-4.el7.noarch
spacewalk-backend-2.9.35-1.el7.noarch
spacewalk-backend-xml-export-libs-2.9.35-1.el7.noarch
spacewalk-backend-config-files-2.9.35-1.el7.noarch
spacewalk-backend-applet-2.9.35-1.el7.noarch
spacewalk-config-2.8.5-1.el7.noarch
spacewalk-reports-2.9.1-1.el7.noarch
python2-spacewalk-certs-tools-2.9.2-1.el7.noarch
spacewalk-setup-2.9.3-1.el7.noarch
spacewalk-postgresql-2.9.1-1.el7.noarch
spacewalk-taskomatic-2.9.31-1.el7.noarch
spacewalk-common-2.9.1-1.el7.noarch
spacewalk-admin-2.9.1-1.el7.noarch
spacewalk-backend-sql-2.9.35-1.el7.noarch
spacewalk-backend-config-files-tool-2.9.35-1.el7.noarch
spacewalk-doc-indexes-2.9.2-1.el7.noarch
spacewalk-java-postgresql-2.9.31-1.el7.noarch
spacewalk-java-2.9.31-1.el7.noarch
spacewalk-backend-tools-2.9.35-1.el7.noarch
spacewalk-setup-postgresql-2.8.4-1.el7.noarch
spacewalk-backend-xmlrpc-2.9.35-1.el7.noarch
spacewalk-usix-2.9.1-1.el7.noarch


[root@us3-inf-lu-s01 ~]# spacewalk-service status
● postgresql.service - PostgreSQL database server
   Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled;
vendor preset: disabled)
   Active: active (running) since Fri 2019-10-04 11:53:53 EDT; 4min 42s
ago
  Process: 1348 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
${PGPORT} -w -t 300 (code=exited, status=0/SUCCESS)
  Process: 1320 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA}
(code=exited, status=0/SUCCESS)
 Main PID: 1400 (postgres)
   CGroup: /system.slice/postgresql.service
   ├─ 1400 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
   ├─ 1441

[Spacewalk-list] Ongoing Jabberd issues on SW 2.9/Centos7 servers

2019-10-04 Thread Larry Clegg

Hello Spacewalkers,

I am continuing to have issues on all my Centos7/Spacewalk 2.9 servers
with Jabberd failing.  It is failing consistently on every server.  I have
verified that all the /etc/jabberd/*.xml files have the same FQDN and same
passwords.  The /etc/pki/spacewalk/jabberd/server.pem includes the same
FQDN.

I just don’t know where else to look and trouble-shoot.

I cannot find any logs for jabberd either:

[root@us3-inf-lu-s01 jabberd]# pwd
/var/lib/jabberd
[root@us3-inf-lu-s01 jabberd]# ls -lR
.:
total 0
drwx-- 2 jabber jabber  65 Oct  4 11:53 db
drwx-- 2 jabber jabber   6 Jul  4  2017 log
drwx-- 2 jabber jabber 105 Sep 17 19:06 pid

./db:
total 8096
-rw-r--r-- 1 jabber jabber  131072 Oct  4 11:53 sqlite.db
-rw-r--r-- 1 jabber jabber   32768 Oct  4 12:26 sqlite.db-shm
-rw-r--r-- 1 jabber jabber 4103552 Oct  4 12:26 sqlite.db-wal

./log:
total 0

./pid:
total 16
-rw-r--r-- 1 jabber jabber 4 Oct  4 11:53 c2s.pid
-rw-r--r-- 1 jabber jabber 4 Oct  4 11:53 router.pid
-rw-r--r-- 1 jabber jabber 4 Oct  4 11:53 s2s.pid
-rw-r--r-- 1 jabber jabber 4 Oct  4 11:53
us3-inf-lu-s01.inf.us3.cloud.kyriba.com.pid
[root@us3-inf-lu-s01 jabberd]#

Environment:
Centos7 with kernel 3.10.0-1062.1.2.el7.x86_64

Spacewalk 2.9
[root@us3-inf-lu-s01 jabberd]# rpm -qa | grep jab
spacewalk-setup-jabberd-2.9.2-1.el7.noarch
jabberpy-0.5-0.27.el7.noarch
jabberd-2.6.1-1.el7.x86_64

[root@us3-inf-lu-s01 jabberd]# rpm -qa | grep java
spacewalk-java-config-2.9.31-1.el7.noarch
java-1.8.0-openjdk-1.8.0.222.b10-1.el7_7.x86_64
javamail-1.4.6-8.el7.noarch
spacewalk-java-lib-2.9.31-1.el7.noarch
java-1.8.0-openjdk-devel-1.8.0.222.b10-1.el7_7.x86_64
java-1.8.0-openjdk-headless-1.8.0.222.b10-1.el7_7.x86_64
javapackages-tools-3.4.1-11.el7.noarch
xz-java-1.3-3.el7.noarch
python-javapackages-3.4.1-11.el7.noarch
javassist-3.16.1-10.el7.noarch
maven-javadoc-plugin-2.10.4-1.sw.noarch
spacewalk-java-postgresql-2.9.31-1.el7.noarch
spacewalk-java-2.9.31-1.el7.noarch
tzdata-java-2019c-1.el7.noarch

[root@us3-inf-lu-s01 ~]# rpm -qa | grep space
spacewalk-base-minimal-config-2.9.4-1.el7.noarch
spacewalk-search-2.9.1-1.el7.noarch
spacewalk-setup-jabberd-2.9.2-1.el7.noarch
spacewalk-schema-2.9.11-1.el7.noarch
spacewalk-remote-utils-2.9.6-1.el7.noarch
spacewalk-backend-app-2.9.35-1.el7.noarch
spacewalk-java-config-2.9.31-1.el7.noarch
spacecmd-2.9.9-1.el7.noarch
spacewalk-dobby-2.9.4-1.el7.noarch
spacewalk-backend-server-2.9.35-1.el7.noarch
spacewalk-backend-iss-2.9.35-1.el7.noarch
perl-XML-NamespaceSupport-1.11-10.el7.noarch
spacewalk-java-lib-2.9.31-1.el7.noarch
python2-spacewalk-usix-2.9.1-1.el7.noarch
spacewalk-backend-config-files-common-2.9.35-1.el7.noarch
spacewalk-backend-libs-2.9.35-1.el7.noarch
spacewalk-backend-iss-export-2.9.35-1.el7.noarch
spacewalk-backend-package-push-server-2.9.35-1.el7.noarch
spacewalk-backend-sql-postgresql-2.9.35-1.el7.noarch
spacewalk-branding-2.9.2-1.el7.noarch
spacewalk-html-2.9.4-1.el7.noarch
spacewalk-certs-tools-2.9.2-1.el7.noarch
spacewalk-selinux-2.9.6-1.el7.noarch
spacewalk-utils-2.9.9-1.el7.noarch
spacewalk-base-minimal-2.9.4-1.el7.noarch
spacewalk-base-2.9.4-1.el7.noarch
spacewalk-repo-2.9-4.el7.noarch
spacewalk-backend-2.9.35-1.el7.noarch
spacewalk-backend-xml-export-libs-2.9.35-1.el7.noarch
spacewalk-backend-config-files-2.9.35-1.el7.noarch
spacewalk-backend-applet-2.9.35-1.el7.noarch
spacewalk-config-2.8.5-1.el7.noarch
spacewalk-reports-2.9.1-1.el7.noarch
python2-spacewalk-certs-tools-2.9.2-1.el7.noarch
spacewalk-setup-2.9.3-1.el7.noarch
spacewalk-postgresql-2.9.1-1.el7.noarch
spacewalk-taskomatic-2.9.31-1.el7.noarch
spacewalk-common-2.9.1-1.el7.noarch
spacewalk-admin-2.9.1-1.el7.noarch
spacewalk-backend-sql-2.9.35-1.el7.noarch
spacewalk-backend-config-files-tool-2.9.35-1.el7.noarch
spacewalk-doc-indexes-2.9.2-1.el7.noarch
spacewalk-java-postgresql-2.9.31-1.el7.noarch
spacewalk-java-2.9.31-1.el7.noarch
spacewalk-backend-tools-2.9.35-1.el7.noarch
spacewalk-setup-postgresql-2.8.4-1.el7.noarch
spacewalk-backend-xmlrpc-2.9.35-1.el7.noarch
spacewalk-usix-2.9.1-1.el7.noarch


[root@us3-inf-lu-s01 ~]# spacewalk-service status
● postgresql.service - PostgreSQL database server
   Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled;
vendor preset: disabled)
   Active: active (running) since Fri 2019-10-04 11:53:53 EDT; 4min 42s
ago
  Process: 1348 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
${PGPORT} -w -t 300 (code=exited, status=0/SUCCESS)
  Process: 1320 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA}
(code=exited, status=0/SUCCESS)
 Main PID: 1400 (postgres)
   CGroup: /system.slice/postgresql.service
   ├─ 1400 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
   ├─ 1441 postgres: logger process
   ├─ 1446 postgres: checkpointer process
   ├─ 1447 postgres: writer process
   ├─ 1448 postgres: wal writer process
   ├─ 1449 postgres: autovacuum launcher process
   ├─ 1450 postgres: stats collector process

Re: [Spacewalk-list] Ongoing Jabberd issues on SW 2.9/Centos7 Servers

Re: [Spacewalk-list] Ongoing Jabberd issues on SW 2.9/Centos7 Servers

Re: [Spacewalk-list] Ongoing Jabberd issues on SW 2.9/Centos7 servers

[Spacewalk-list] Ongoing Jabberd issues on SW 2.9/Centos7 servers

4 matches

Site Navigation

Mail list logo

Footer information