[Spacewalk-list] Error connecting to jabber

[InvalidPath]

Hey everyone. Another person here having the whole can't connect to jabber
server issue.

I've gone through the verifying of hostname, hosts, resolv, etc files.
I've ran the spacewalk-hostname-rename binary.

***@automation:/usr/bin$ /usr/sbin/spacewalk-service status

Redirecting to /bin/systemctl status postgresql.service

● postgresql.service - PostgreSQL database server

Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled;
vendor preset: disabled)
Active: active (running) since Mon 2017-05-22 14:52:07 MDT; 44s ago
Process: 15302 ExecStop=/usr/bin/pg_ctl stop -D ${PGDATA} -s -m fast
(code=exited, status=0/SUCCESS)
Process: 15331 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
${PGPORT} -w -t 300 (code=exited, status
=0/SUCCESS)
Process: 15325 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA}
(code=exited, status=0/SUCCESS)
Main PID: 15334 (postgres)
CGroup: /system.slice/postgresql.service
├─15334 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
├─15335 postgres: logger process
├─15337 postgres: checkpointer process
├─15338 postgres: writer process
├─15339 postgres: wal writer process
├─15340 postgres: autovacuum launcher process
├─15341 postgres: stats collector process
├─15449 postgres: rhnuser rhnschema 127.0.0.1(50548) idle
├─15450 postgres: rhnuser rhnschema 127.0.0.1(50549) idle
├─15451 postgres: rhnuser rhnschema 127.0.0.1(50552) idle
├─15452 postgres: rhnuser rhnschema 127.0.0.1(50554) idle
├─15453 postgres: rhnuser rhnschema 127.0.0.1(50556) idle
├─15737 postgres: rhnuser rhnschema 127.0.0.1(50560) idle
├─15738 postgres: rhnuser rhnschema 127.0.0.1(50563) idle
├─15739 postgres: rhnuser rhnschema 127.0.0.1(50562) idle
├─15740 postgres: rhnuser rhnschema 127.0.0.1(50566) idle
├─15741 postgres: rhnuser rhnschema 127.0.0.1(50568) idle
├─15742 postgres: rhnuser rhnschema 127.0.0.1(50570) idle
├─15743 postgres: rhnuser rhnschema 127.0.0.1(50572) idle
├─15744 postgres: rhnuser rhnschema 127.0.0.1(50574) idle
├─15745 postgres: rhnuser rhnschema 127.0.0.1(50576) idle
├─15781 postgres: rhnuser rhnschema 127.0.0.1(50580) idle
├─15828 postgres: rhnuser rhnschema 127.0.0.1(50582) idle
├─15829 postgres: rhnuser rhnschema 127.0.0.1(50584) idle
├─15830 postgres: rhnuser rhnschema 127.0.0.1(50586) idle
├─15831 postgres: rhnuser rhnschema 127.0.0.1(50588) idle
├─15832 postgres: rhnuser rhnschema 127.0.0.1(50590) idle
├─15835 postgres: rhnuser rhnschema 127.0.0.1(50592) idle
├─15841 postgres: rhnuser rhnschema 127.0.0.1(50606) idle
├─15842 postgres: rhnuser rhnschema 127.0.0.1(50608) idle
└─15844 postgres: rhnuser rhnschema 127.0.0.1(50612) idle

May 22 14:52:06 automation.egovmt.com systemd[1]: Starting PostgreSQL
database server...
May 22 14:52:07 automation.egovmt.com systemd[1]: Started PostgreSQL
database server.
Redirecting to /bin/systemctl status jabberd.service
● jabberd.service - Jabber Server
Loaded: loaded (/usr/lib/systemd/system/jabberd.service; enabled; vendor
preset: disabled)
Active: inactive (dead) since Mon 2017-05-22 14:52:07 MDT; 44s ago
Process: 15362 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 15362 (code=exited, status=0/SUCCESS)

May 22 14:52:07 automation.egovmt.com systemd[1]: Starting Jabber Server...
May 22 14:52:07 automation.egovmt.com systemd[1]: Started Jabber Server.
May 22 14:52:07 automation.egovmt.com systemd[1]: Stopped Jabber Server.
May 22 14:52:07 automation.egovmt.com systemd[1]: Stopping Jabber Server...
Redirecting to /bin/systemctl status tomcat.service
● tomcat.service - Apache Tomcat Web Application Container
Loaded: loaded (/usr/lib/systemd/system/tomcat.service; enabled; vendor
preset: disabled)
Active: active (running) since Mon 2017-05-22 14:52:07 MDT; 44s ago
Main PID: 15381 (java)
CGroup: /system.slice/tomcat.service
└─15381 /usr/lib/jvm/jre/bin/java -ea -Xms256m -Xmx256m
-Djava.awt.headless=true -Dorg.xml.sax.dr...

May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017 2:52:34
PM org.apache.catalina.startup....tor
May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Deployment of
configuration descriptor /etc/to... ms
May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017 2:52:34
PM org.apache.coyote.AbstractPr...art
May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Starting
ProtocolHandler ["http-bio-127.0.0.1-8080"]
May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017 2:52:34
PM org.apache.coyote.AbstractPr...art
May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Starting
ProtocolHandler ["ajp-bio-127.0.0.1-8009"]
May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017 2:52:34
PM org.apache.coyote.AbstractPr...art
May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Starting
ProtocolHandler ["ajp-bio-0:0:0:0:0:0...9"]
May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017 2:52:34
PM org.apache.catalina.startup....art
May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Server startup
in 26364 ms
Hint: Some lines were ellipsized, use -l to show in full.
Redirecting to /bin/systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor
preset: disabled)
Active: active (running) since Mon 2017-05-22 14:52:34 MDT; 16s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 15127 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited,
status=0/SUCCESS)
Main PID: 15538 (httpd)
Status: "Total requests: 7; Current requests/sec: 0.778; Current traffic:
568 B/sec"
CGroup: /system.slice/httpd.service
├─15538 /usr/sbin/httpd -DFOREGROUND
├─15539 /usr/sbin/httpd -DFOREGROUND
├─15540 /usr/sbin/httpd -DFOREGROUND
├─15541 /usr/sbin/httpd -DFOREGROUND
├─15542 /usr/sbin/httpd -DFOREGROUND
├─15543 /usr/sbin/httpd -DFOREGROUND
├─15544 /usr/sbin/httpd -DFOREGROUND
├─15545 /usr/sbin/httpd -DFOREGROUND
└─15546 /usr/sbin/httpd -DFOREGROUND

May 22 14:52:34 automation.egovmt.com systemd[1]: Starting The Apache HTTP
Server...
May 22 14:52:34 automation.egovmt.com systemd[1]: Started The Apache HTTP
Server.
Redirecting to /bin/systemctl status osa-dispatcher.service
● osa-dispatcher.service - OSA Dispatcher daemon
Loaded: loaded (/usr/lib/systemd/system/osa-dispatcher.service; enabled;
vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2017-05-22 14:52:35 MDT; 16s
ago
Process: 15564 ExecStart=/usr/sbin/osa-dispatcher --pid-file
/var/run/osa-dispatcher.pid (code=exited, status
=255)


Process: 15562 ExecStartPre=/bin/rm -f /var/run/osa-dispatcher.pid
(code=exited, status=0/SUCCESS)
Main PID: 2051 (code=killed, signal=TERM)

May 22 14:52:34 automation.egovmt.com systemd[1]: Starting OSA Dispatcher
daemon...
May 22 14:52:35 automation.egovmt.com osa-dispatcher[15564]: Spacewalk
15564 2017/05/22 14:52:35 -06:00: (...,)
May 22 14:52:35 automation.egovmt.com osa-dispatcher[15564]: Spacewalk
15564 2017/05/22 14:52:35 -06:00: (...,)
May 22 14:52:35 automation.egovmt.com osa-dispatcher[15564]: ERROR:
unhandled exception occurred: (unicode...).
May 22 14:52:35 automation.egovmt.com systemd[1]: osa-dispatcher.service:
control process exited, code=e...=255
May 22 14:52:35 automation.egovmt.com systemd[1]: Failed to start OSA
Dispatcher daemon.
May 22 14:52:35 automation.egovmt.com systemd[1]: Unit
osa-dispatcher.service entered failed state.
May 22 14:52:35 automation.egovmt.com systemd[1]: osa-dispatcher.service
failed.
Hint: Some lines were ellipsized, use -l to show in full.
Redirecting to /bin/systemctl status rhn-search.service
● rhn-search.service - Spacewalk search engine
Loaded: loaded (/usr/lib/systemd/system/rhn-search.service; enabled;
vendor preset: disabled)
Active: active (running) since Mon 2017-05-22 14:52:35 MDT; 16s ago
Process: 15043 ExecStop=/usr/sbin/rhn-search stop (code=exited,
status=0/SUCCESS)
Process: 15583 ExecStart=/usr/sbin/rhn-search start (code=exited,
status=0/SUCCESS)
Main PID: 15596 (rhnsearchd)
CGroup: /system.slice/rhn-search.service
├─15596 /usr/bin/rhnsearchd
/usr/share/rhn/config-defaults/rhn_search_daemon.conf wrapper.pidfile...
└─15598 /usr/bin/java
-Djava.library.path=/usr/lib:/usr/lib64:/usr/lib/oracle/11.2/client/lib:/us...


May 22 14:52:35 automation.egovmt.com systemd[1]: Starting Spacewalk search
engine...
May 22 14:52:35 automation.egovmt.com rhn-search[15583]: Starting
rhn-search...
May 22 14:52:35 automation.egovmt.com systemd[1]: Started Spacewalk search
engine.
● cobblerd.service - LSB: daemon for libvirt virtualization API
Loaded: loaded (/etc/rc.d/init.d/cobblerd; bad; vendor preset: disabled)
Active: active (running) since Mon 2017-05-22 14:52:36 MDT; 15s ago
Docs: man:systemd-sysv-generator(8)
Process: 15017 ExecStop=/etc/rc.d/init.d/cobblerd stop (code=exited,
status=0/SUCCESS)
Process: 15639 ExecStart=/etc/rc.d/init.d/cobblerd start (code=exited,
status=0/SUCCESS)
CGroup: /system.slice/cobblerd.service
└─15649 /usr/bin/python -s /bin/cobblerd --daemonize

May 22 14:52:35 automation.egovmt.com systemd[1]: Starting LSB: daemon for
libvirt virtualization API...
May 22 14:52:36 automation.egovmt.com cobblerd[15639]: Starting cobbler
daemon: [ OK ]
May 22 14:52:36 automation.egovmt.com systemd[1]: Started LSB: daemon for
libvirt virtualization API.
Redirecting to /bin/systemctl status taskomatic.service
● taskomatic.service - Taskomatic
Loaded: loaded (/usr/lib/systemd/system/taskomatic.service; enabled;
vendor preset: disabled)
Active: active (running) since Mon 2017-05-22 14:52:36 MDT; 14s ago
Process: 14942 ExecStop=/usr/sbin/taskomatic stop (code=exited,
status=0/SUCCESS)
Process: 15677 ExecStart=/usr/sbin/taskomatic start (code=exited,
status=0/SUCCESS)
Main PID: 15691 (taskomaticd)
CGroup: /system.slice/taskomatic.service
├─15691 /usr/bin/taskomaticd
/usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf wrapper.pi...
└─15746 /usr/bin/java -Dibm.dst.compatibility=true
-Dfile.encoding=UTF-8 -Xms256m -Xmx1024m -Djav...

May 22 14:52:36 automation.egovmt.com systemd[1]: Starting Taskomatic...
May 22 14:52:36 automation.egovmt.com taskomatic[15677]: Starting RHN
Taskomatic...
May 22 14:52:36 automation.egovmt.com wrapper[15691]: --> Wrapper Started
as Daemon
May 22 14:52:36 automation.egovmt.com wrapper[15691]: Launching a JVM...
May 22 14:52:36 automation.egovmt.com systemd[1]: Started Taskomatic.


***@automation:/usr/sbin$ ./osa-dispatcher

Spacewalk 15975 2017/05/22 14:53:07 -06:00: ('Error connecting to jabber
server: Unable to connect to the host
and port specified. See https://access.redhat.com/solutions/327903 for more
information. ',)
Spacewalk 15975 2017/05/22 14:53:07 -06:00: ('Error caught:',)



ERROR: unhandled exception occurred: (unicode argument expected, got
'str').
***@automation:/usr/sbin$ ***@automation:/usr/sbin$ ./osa-dispatcher

Spacewalk 15975 2017/05/22 14:53:07 -06:00: ('Error connecting to jabber
server: Unable to connect to the host
and port specified. See https://access.redhat.com/solutions/327903 for more
information. ',)
Spacewalk 15975 2017/05/22 14:53:07 -06:00: ('Error caught:',)



ERROR: unhandled exception occurred: (unicode argument expected, got
'str').
***@automation:/usr/sbin$ semanage permissive -a osad_t



Hopefully someone here can point me in the right direction.

Thanks!!

[Leonardo Barros]

Hi,

You can try this: https://access.redhat.com/solutions/327903



Em seg, 22 de mai de 2017 às 18:18, InvalidPath <***@gmail.com>
escreveu:

> Hey everyone. Another person here having the whole can't connect to
> jabber server issue.
>
> I've gone through the verifying of hostname, hosts, resolv, etc files.
> I've ran the spacewalk-hostname-rename binary.
>
> ***@automation:/usr/bin$ /usr/sbin/spacewalk-service status
>
> Redirecting to /bin/systemctl status postgresql.service
>
> ● postgresql.service - PostgreSQL database server
>
> Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled;
> vendor preset: disabled)
> Active: active (running) since Mon 2017-05-22 14:52:07 MDT; 44s ago
> Process: 15302 ExecStop=/usr/bin/pg_ctl stop -D ${PGDATA} -s -m fast
> (code=exited, status=0/SUCCESS)
> Process: 15331 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
> ${PGPORT} -w -t 300 (code=exited, status
> =0/SUCCESS)
> Process: 15325 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA}
> (code=exited, status=0/SUCCESS)
> Main PID: 15334 (postgres)
> CGroup: /system.slice/postgresql.service
> ├─15334 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
> ├─15335 postgres: logger process
> ├─15337 postgres: checkpointer process
> ├─15338 postgres: writer process
> ├─15339 postgres: wal writer process
> ├─15340 postgres: autovacuum launcher process
> ├─15341 postgres: stats collector process
> ├─15449 postgres: rhnuser rhnschema 127.0.0.1(50548) idle
> ├─15450 postgres: rhnuser rhnschema 127.0.0.1(50549) idle
> ├─15451 postgres: rhnuser rhnschema 127.0.0.1(50552) idle
> ├─15452 postgres: rhnuser rhnschema 127.0.0.1(50554) idle
> ├─15453 postgres: rhnuser rhnschema 127.0.0.1(50556) idle
> ├─15737 postgres: rhnuser rhnschema 127.0.0.1(50560) idle
> ├─15738 postgres: rhnuser rhnschema 127.0.0.1(50563) idle
> ├─15739 postgres: rhnuser rhnschema 127.0.0.1(50562) idle
> ├─15740 postgres: rhnuser rhnschema 127.0.0.1(50566) idle
> ├─15741 postgres: rhnuser rhnschema 127.0.0.1(50568) idle
> ├─15742 postgres: rhnuser rhnschema 127.0.0.1(50570) idle
> ├─15743 postgres: rhnuser rhnschema 127.0.0.1(50572) idle
> ├─15744 postgres: rhnuser rhnschema 127.0.0.1(50574) idle
> ├─15745 postgres: rhnuser rhnschema 127.0.0.1(50576) idle
> ├─15781 postgres: rhnuser rhnschema 127.0.0.1(50580) idle
> ├─15828 postgres: rhnuser rhnschema 127.0.0.1(50582) idle
> ├─15829 postgres: rhnuser rhnschema 127.0.0.1(50584) idle
> ├─15830 postgres: rhnuser rhnschema 127.0.0.1(50586) idle
> ├─15831 postgres: rhnuser rhnschema 127.0.0.1(50588) idle
> ├─15832 postgres: rhnuser rhnschema 127.0.0.1(50590) idle
> ├─15835 postgres: rhnuser rhnschema 127.0.0.1(50592) idle
> ├─15841 postgres: rhnuser rhnschema 127.0.0.1(50606) idle
> ├─15842 postgres: rhnuser rhnschema 127.0.0.1(50608) idle
> └─15844 postgres: rhnuser rhnschema 127.0.0.1(50612) idle
>
> May 22 14:52:06 automation.egovmt.com systemd[1]: Starting PostgreSQL
> database server...
> May 22 14:52:07 automation.egovmt.com systemd[1]: Started PostgreSQL
> database server.
> Redirecting to /bin/systemctl status jabberd.service
> ● jabberd.service - Jabber Server
> Loaded: loaded (/usr/lib/systemd/system/jabberd.service; enabled; vendor
> preset: disabled)
> Active: inactive (dead) since Mon 2017-05-22 14:52:07 MDT; 44s ago
> Process: 15362 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
> Main PID: 15362 (code=exited, status=0/SUCCESS)
>
> May 22 14:52:07 automation.egovmt.com systemd[1]: Starting Jabber
> Server...
> May 22 14:52:07 automation.egovmt.com systemd[1]: Started Jabber Server.
> May 22 14:52:07 automation.egovmt.com systemd[1]: Stopped Jabber Server.
> May 22 14:52:07 automation.egovmt.com systemd[1]: Stopping Jabber
> Server...
> Redirecting to /bin/systemctl status tomcat.service
> ● tomcat.service - Apache Tomcat Web Application Container
> Loaded: loaded (/usr/lib/systemd/system/tomcat.service; enabled; vendor
> preset: disabled)
> Active: active (running) since Mon 2017-05-22 14:52:07 MDT; 44s ago
> Main PID: 15381 (java)
> CGroup: /system.slice/tomcat.service
> └─15381 /usr/lib/jvm/jre/bin/java -ea -Xms256m -Xmx256m
> -Djava.awt.headless=true -Dorg.xml.sax.dr...
>
> May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017 2:52:34
> PM org.apache.catalina.startup....tor
> May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Deployment of
> configuration descriptor /etc/to... ms
> May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017 2:52:34
> PM org.apache.coyote.AbstractPr...art
> May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Starting
> ProtocolHandler ["http-bio-127.0.0.1-8080"]
> May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017 2:52:34
> PM org.apache.coyote.AbstractPr...art
> May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Starting
> ProtocolHandler ["ajp-bio-127.0.0.1-8009"]
> May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017 2:52:34
> PM org.apache.coyote.AbstractPr...art
> May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Starting
> ProtocolHandler ["ajp-bio-0:0:0:0:0:0...9"]
> May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017 2:52:34
> PM org.apache.catalina.startup....art
> May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Server startup
> in 26364 ms
> Hint: Some lines were ellipsized, use -l to show in full.
> Redirecting to /bin/systemctl status httpd.service
> ● httpd.service - The Apache HTTP Server
> Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor
> preset: disabled)
> Active: active (running) since Mon 2017-05-22 14:52:34 MDT; 16s ago
> Docs: man:httpd(8)
> man:apachectl(8)
> Process: 15127 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited,
> status=0/SUCCESS)
> Main PID: 15538 (httpd)
> Status: "Total requests: 7; Current requests/sec: 0.778; Current
> traffic: 568 B/sec"
> CGroup: /system.slice/httpd.service
> ├─15538 /usr/sbin/httpd -DFOREGROUND
> ├─15539 /usr/sbin/httpd -DFOREGROUND
> ├─15540 /usr/sbin/httpd -DFOREGROUND
> ├─15541 /usr/sbin/httpd -DFOREGROUND
> ├─15542 /usr/sbin/httpd -DFOREGROUND
> ├─15543 /usr/sbin/httpd -DFOREGROUND
> ├─15544 /usr/sbin/httpd -DFOREGROUND
> ├─15545 /usr/sbin/httpd -DFOREGROUND
> └─15546 /usr/sbin/httpd -DFOREGROUND
>
> May 22 14:52:34 automation.egovmt.com systemd[1]: Starting The Apache
> HTTP Server...
> May 22 14:52:34 automation.egovmt.com systemd[1]: Started The Apache HTTP
> Server.
> Redirecting to /bin/systemctl status osa-dispatcher.service
> ● osa-dispatcher.service - OSA Dispatcher daemon
> Loaded: loaded (/usr/lib/systemd/system/osa-dispatcher.service; enabled;
> vendor preset: disabled)
> Active: failed (Result: exit-code) since Mon 2017-05-22 14:52:35 MDT;
> 16s ago
> Process: 15564 ExecStart=/usr/sbin/osa-dispatcher --pid-file
> /var/run/osa-dispatcher.pid (code=exited, status
> =255)
>
>
> Process: 15562 ExecStartPre=/bin/rm -f /var/run/osa-dispatcher.pid
> (code=exited, status=0/SUCCESS)
> Main PID: 2051 (code=killed, signal=TERM)
>
> May 22 14:52:34 automation.egovmt.com systemd[1]: Starting OSA Dispatcher
> daemon...
> May 22 14:52:35 automation.egovmt.com osa-dispatcher[15564]: Spacewalk
> 15564 2017/05/22 14:52:35 -06:00: (...,)
> May 22 14:52:35 automation.egovmt.com osa-dispatcher[15564]: Spacewalk
> 15564 2017/05/22 14:52:35 -06:00: (...,)
> May 22 14:52:35 automation.egovmt.com osa-dispatcher[15564]: ERROR:
> unhandled exception occurred: (unicode...).
> May 22 14:52:35 automation.egovmt.com systemd[1]: osa-dispatcher.service:
> control process exited, code=e...=255
> May 22 14:52:35 automation.egovmt.com systemd[1]: Failed to start OSA
> Dispatcher daemon.
> May 22 14:52:35 automation.egovmt.com systemd[1]: Unit
> osa-dispatcher.service entered failed state.
> May 22 14:52:35 automation.egovmt.com systemd[1]: osa-dispatcher.service
> failed.
> Hint: Some lines were ellipsized, use -l to show in full.
> Redirecting to /bin/systemctl status rhn-search.service
> ● rhn-search.service - Spacewalk search engine
> Loaded: loaded (/usr/lib/systemd/system/rhn-search.service; enabled;
> vendor preset: disabled)
> Active: active (running) since Mon 2017-05-22 14:52:35 MDT; 16s ago
> Process: 15043 ExecStop=/usr/sbin/rhn-search stop (code=exited,
> status=0/SUCCESS)
> Process: 15583 ExecStart=/usr/sbin/rhn-search start (code=exited,
> status=0/SUCCESS)
> Main PID: 15596 (rhnsearchd)
> CGroup: /system.slice/rhn-search.service
> ├─15596 /usr/bin/rhnsearchd
> /usr/share/rhn/config-defaults/rhn_search_daemon.conf wrapper.pidfile...
> └─15598 /usr/bin/java
> -Djava.library.path=/usr/lib:/usr/lib64:/usr/lib/oracle/11.2/client/lib:/us...
>
>
> May 22 14:52:35 automation.egovmt.com systemd[1]: Starting Spacewalk
> search engine...
> May 22 14:52:35 automation.egovmt.com rhn-search[15583]: Starting
> rhn-search...
> May 22 14:52:35 automation.egovmt.com systemd[1]: Started Spacewalk
> search engine.
> ● cobblerd.service - LSB: daemon for libvirt virtualization API
> Loaded: loaded (/etc/rc.d/init.d/cobblerd; bad; vendor preset: disabled)
> Active: active (running) since Mon 2017-05-22 14:52:36 MDT; 15s ago
> Docs: man:systemd-sysv-generator(8)
> Process: 15017 ExecStop=/etc/rc.d/init.d/cobblerd stop (code=exited,
> status=0/SUCCESS)
> Process: 15639 ExecStart=/etc/rc.d/init.d/cobblerd start (code=exited,
> status=0/SUCCESS)
> CGroup: /system.slice/cobblerd.service
> └─15649 /usr/bin/python -s /bin/cobblerd --daemonize
>
> May 22 14:52:35 automation.egovmt.com systemd[1]: Starting LSB: daemon
> for libvirt virtualization API...
> May 22 14:52:36 automation.egovmt.com cobblerd[15639]: Starting cobbler
> daemon: [ OK ]
> May 22 14:52:36 automation.egovmt.com systemd[1]: Started LSB: daemon for
> libvirt virtualization API.
> Redirecting to /bin/systemctl status taskomatic.service
> ● taskomatic.service - Taskomatic
> Loaded: loaded (/usr/lib/systemd/system/taskomatic.service; enabled;
> vendor preset: disabled)
> Active: active (running) since Mon 2017-05-22 14:52:36 MDT; 14s ago
> Process: 14942 ExecStop=/usr/sbin/taskomatic stop (code=exited,
> status=0/SUCCESS)
> Process: 15677 ExecStart=/usr/sbin/taskomatic start (code=exited,
> status=0/SUCCESS)
> Main PID: 15691 (taskomaticd)
> CGroup: /system.slice/taskomatic.service
> ├─15691 /usr/bin/taskomaticd
> /usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf wrapper.pi...
> └─15746 /usr/bin/java -Dibm.dst.compatibility=true
> -Dfile.encoding=UTF-8 -Xms256m -Xmx1024m -Djav...
>
> May 22 14:52:36 automation.egovmt.com systemd[1]: Starting Taskomatic...
> May 22 14:52:36 automation.egovmt.com taskomatic[15677]: Starting RHN
> Taskomatic...
> May 22 14:52:36 automation.egovmt.com wrapper[15691]: --> Wrapper Started
> as Daemon
> May 22 14:52:36 automation.egovmt.com wrapper[15691]: Launching a JVM...
> May 22 14:52:36 automation.egovmt.com systemd[1]: Started Taskomatic.
>
>
> ***@automation:/usr/sbin$ ./osa-dispatcher
>
> Spacewalk 15975 2017/05/22 14:53:07 -06:00: ('Error connecting to jabber
> server: Unable to connect to the host
> and port specified. See https://access.redhat.com/solutions/327903 for
> more information. ',)
> Spacewalk 15975 2017/05/22 14:53:07 -06:00: ('Error caught:',)
>
>
>
>
> ERROR: unhandled exception occurred: (unicode argument expected, got
> 'str').
> ***@automation:/usr/sbin$ ***@automation:/usr/sbin$ ./osa-dispatcher
>
> Spacewalk 15975 2017/05/22 14:53:07 -06:00: ('Error connecting to jabber
> server: Unable to connect to the host
> and port specified. See https://access.redhat.com/solutions/327903 for
> more information. ',)
> Spacewalk 15975 2017/05/22 14:53:07 -06:00: ('Error caught:',)
>
>
>
>
> ERROR: unhandled exception occurred: (unicode argument expected, got
> 'str').
> ***@automation:/usr/sbin$ semanage permissive -a osad_t
>
>
>
> Hopefully someone here can point me in the right direction.
>
> Thanks!!
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-***@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list

[Fouts, Christopher]

This post might be inappropriate. Click to display it.

[Michael Mraka]

Fouts, Christopher:
> From that page,
>
> “Then reconfigure jabberd and restart the Satellite services”
>
> What (re)configuration does jabberd need?

Hi Chris,

try to look at
https://github.com/spacewalkproject/spacewalk/wiki/OsadHowTo
https://github.com/spacewalkproject/spacewalk/wiki/JabberAndOSAD

BTW in nightly version (upcomming 2.7) we've changed default jabberd
backend from berkeleydb to sqlite which seems to be more reliable.

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

[Wilkinson, Matthew]

Wow that will be a most welcome change! I've encountered and ongoing issue with berkelyDB and jabber so I welcome this change.

--Matthew Wilkinson


-----Original Message-----
From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Michael Mraka
Sent: Wednesday, May 31, 2017 02:35
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

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

**********************************************************************
Fouts, Christopher:
> From that page,
>
> “Then reconfigure jabberd and restart the Satellite services”
>
> What (re)configuration does jabberd need?

Hi Chris,

try to look at
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_spacewalkproject_spacewalk_wiki_OsadHowTo&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=UOkDF6QbGDfXvQYKqfGHx-8OQQnNvWfIWrphxwZ7byQ&s=s1Mc8MGnG2Dz_rIXycg3BBq1JkQ3YI1GUM-Oo_7M22I&e=
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_spacewalkproject_spacewalk_wiki_JabberAndOSAD&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=UOkDF6QbGDfXvQYKqfGHx-8OQQnNvWfIWrphxwZ7byQ&s=PH5yheuhVhlEKmtsozQXGDzrtyI5EtGfVfILlcEZJpk&e=

BTW in nightly version (upcomming 2.7) we've changed default jabberd backend from berkeleydb to sqlite which seems to be more reliable.

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

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

[Ree, Jan-Albert van]

While I agree that sqlite is better than berkeleydb why not make PostgreSQL the default if the PostgreSQL database is already being set up during installation ( ie spacewalk-setup-postgresql is called )
Our modest installation (roughly 80 clients) still wasn't rock solid using sqlite (instead of crashing almost daily it became a 'once a month' thing where the DB got corrupted), only after moving to PostgreSQL do we now have an osa-dispatcher/jabber/osad setup which requires virtually no maintenance and is pretty much crash-proof.

Regards,
--
Jan-Albert


Jan-Albert van Ree | Linux System Administrator | MARIN Support Group
MARIN | T [phone] | mailto:***@marin.nl | http://www.marin.nl

MARIN news: http://www.marin.nl/web/News/News-items/Zeeen-zonder-zwavel-Het-Financieele-Dagblad.htm

________________________________________
From: spacewalk-list-***@redhat.com <spacewalk-list-***@redhat.com> on behalf of Michael Mraka <***@redhat.com>
Sent: Wednesday, May 31, 2017 09:35
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

Fouts, Christopher:
> From that page,
>
> “Then reconfigure jabberd and restart the Satellite services”
>
> What (re)configuration does jabberd need?

Hi Chris,

try to look at
https://github.com/spacewalkproject/spacewalk/wiki/OsadHowTo
https://github.com/spacewalkproject/spacewalk/wiki/JabberAndOSAD

BTW in nightly version (upcomming 2.7) we've changed default jabberd
backend from berkeleydb to sqlite which seems to be more reliable.

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

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

[Wilkinson, Matthew]

This is a good point. I didn't realize some users already had sqlite installations of jabberd.

--Matthew Wilkinson


-----Original Message-----
From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Ree, Jan-Albert van
Sent: Wednesday, May 31, 2017 10:15
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

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

**********************************************************************
While I agree that sqlite is better than berkeleydb why not make PostgreSQL the default if the PostgreSQL database is already being set up during installation ( ie spacewalk-setup-postgresql is called ) Our modest installation (roughly 80 clients) still wasn't rock solid using sqlite (instead of crashing almost daily it became a 'once a month' thing where the DB got corrupted), only after moving to PostgreSQL do we now have an osa-dispatcher/jabber/osad setup which requires virtually no maintenance and is pretty much crash-proof.

Regards,
--
Jan-Albert


Jan-Albert van Ree | Linux System Administrator | MARIN Support Group MARIN | T [phone] | mailto:***@marin.nl | https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marin.nl&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=qjeOwDtujQBOws11lvjQhdsuf4D_JH6bQEBZ3mwgP-Y&e=

MARIN news: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marin.nl_web_News_News-2Ditems_Zeeen-2Dzonder-2Dzwavel-2DHet-2DFinancieele-2DDagblad.htm&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=zEMSlWEfa5cAfxj_XJf8ri9r8nuXqZ2uLimvHOTkzj4&e=

________________________________________
From: spacewalk-list-***@redhat.com <spacewalk-list-***@redhat.com> on behalf of Michael Mraka <https://urldefense.proofpoint.com/v2/url?u=http-3A__michael.mraka-40redhat.com&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=ZV9A48T4fug2EDxquJwPgqYu5Hk7bzQs8mhd4rDoJxo&e= >
Sent: Wednesday, May 31, 2017 09:35
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

Fouts, Christopher:
> From that page,
>
> “Then reconfigure jabberd and restart the Satellite services”
>
> What (re)configuration does jabberd need?

Hi Chris,

try to look at
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_spacewalkproject_spacewalk_wiki_OsadHowTo&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=E-9ed2yJu3fClL1Fm74mtGyG8c6zylJ-N5YVaueNvyA&e=
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_spacewalkproject_spacewalk_wiki_JabberAndOSAD&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=S8B3sT8rAh4g8YJ7LZHlTNLu9RmrhZ9phoY5CZTpDe0&e=

BTW in nightly version (upcomming 2.7) we've changed default jabberd backend from berkeleydb to sqlite which seems to be more reliable.

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

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

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

[Matthias Gruber]

Hi!

We also switched fast after the installation of 2.5 to sqlite, berkeley
was quite bad, well even the sqlite sometimes has problems, we have a lot
of Proxy-Server and several hundered of clients
I am thinking of moving to the postgres, but dont have the time at the
moment

cheers
Matthias



Von: "Wilkinson, Matthew" <***@alliantenergy.com>
An: "spacewalk-***@redhat.com" <spacewalk-***@redhat.com>
Datum: 31.05.2017 17:48
Betreff: Re: [Spacewalk-list] Error connecting to jabber
Gesendet von: spacewalk-list-***@redhat.com



This is a good point. I didn't realize some users already had sqlite
installations of jabberd.

--Matthew Wilkinson


-----Original Message-----
From: spacewalk-list-***@redhat.com [
mailto:spacewalk-list-***@redhat.com] On Behalf Of Ree, Jan-Albert van
Sent: Wednesday, May 31, 2017 10:15
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

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

**********************************************************************
While I agree that sqlite is better than berkeleydb why not make
PostgreSQL the default if the PostgreSQL database is already being set up
during installation ( ie spacewalk-setup-postgresql is called ) Our modest
installation (roughly 80 clients) still wasn't rock solid using sqlite
(instead of crashing almost daily it became a 'once a month' thing where
the DB got corrupted), only after moving to PostgreSQL do we now have an
osa-dispatcher/jabber/osad setup which requires virtually no maintenance
and is pretty much crash-proof.

Regards,
--
Jan-Albert


Jan-Albert van Ree | Linux System Administrator | MARIN Support Group
MARIN | T [phone] | mailto:***@marin.nl |
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marin.nl&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=qjeOwDtujQBOws11lvjQhdsuf4D_JH6bQEBZ3mwgP-Y&e=


MARIN news:
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marin.nl_web_News_News-2Ditems_Zeeen-2Dzonder-2Dzwavel-2DHet-2DFinancieele-2DDagblad.htm&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=zEMSlWEfa5cAfxj_XJf8ri9r8nuXqZ2uLimvHOTkzj4&e=


________________________________________
From: spacewalk-list-***@redhat.com
<spacewalk-list-***@redhat.com> on behalf of Michael Mraka <
https://urldefense.proofpoint.com/v2/url?u=http-3A__michael.mraka-40redhat.com&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=ZV9A48T4fug2EDxquJwPgqYu5Hk7bzQs8mhd4rDoJxo&e=
>
Sent: Wednesday, May 31, 2017 09:35
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

Fouts, Christopher:
> From that page,
>
> “Then reconfigure jabberd and restart the Satellite services”
>
> What (re)configuration does jabberd need?

Hi Chris,

try to look at
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_spacewalkproject_spacewalk_wiki_OsadHowTo&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=E-9ed2yJu3fClL1Fm74mtGyG8c6zylJ-N5YVaueNvyA&e=

https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_spacewalkproject_spacewalk_wiki_JabberAndOSAD&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=S8B3sT8rAh4g8YJ7LZHlTNLu9RmrhZ9phoY5CZTpDe0&e=


BTW in nightly version (upcomming 2.7) we've changed default jabberd
backend from berkeleydb to sqlite which seems to be more reliable.

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

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

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

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




Persönlich haftende Gesellschafter: Harald Illy, Michael Klaus, Friedrich von Metzler, Emmerich MÌller, Dr. Johannes J. Reich, Gerhard Wiesheu
Vorsitzender des Aufsichtsrates: Dr. Christoph SchÃŒcking
Sitz der Gesellschaft: Frankfurt am Main, Handelsregisternummer: HRB 27 515

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene EmpfÀnger sein, so bitten wir Sie höflich, dies unverzÌglich dem Absender mitzuteilen und die Nachricht zu löschen. Es ist unzulÀssig, die Nachricht unbefugt weiterzuleiten oder zu kopieren. Da wir nicht die Echtheit oder VollstÀndigkeit der in dieser Nachricht enthaltenen Informationen garantieren oder zusichern können, sind die vorstehenden AusfÌhrungen rechtlich nicht bindend. Eine Haftung hierfÌr wird ausgeschlossen.
This message is confidential. If you are not the intended recipient, we kindly ask you to inform the sender and delete the information. Any unauthorised dissemination or copying hereof is prohibited. As we cannot guarantee or assure the genuineness or completeness of the information contained in this message, the statements set forth above are not legally binding. Accordingly we cannot accept any liability for their contents.

[Wilkinson, Matthew]

Can I ask how you configured jabber to use PostgreSQL?

--Matthew Wilkinson


-----Original Message-----
From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Ree, Jan-Albert van
Sent: Wednesday, May 31, 2017 10:15
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

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

**********************************************************************
While I agree that sqlite is better than berkeleydb why not make PostgreSQL the default if the PostgreSQL database is already being set up during installation ( ie spacewalk-setup-postgresql is called ) Our modest installation (roughly 80 clients) still wasn't rock solid using sqlite (instead of crashing almost daily it became a 'once a month' thing where the DB got corrupted), only after moving to PostgreSQL do we now have an osa-dispatcher/jabber/osad setup which requires virtually no maintenance and is pretty much crash-proof.

Regards,
--
Jan-Albert


Jan-Albert van Ree | Linux System Administrator | MARIN Support Group MARIN | T [phone] | mailto:***@marin.nl | https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marin.nl&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=qjeOwDtujQBOws11lvjQhdsuf4D_JH6bQEBZ3mwgP-Y&e=

MARIN news: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marin.nl_web_News_News-2Ditems_Zeeen-2Dzonder-2Dzwavel-2DHet-2DFinancieele-2DDagblad.htm&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=zEMSlWEfa5cAfxj_XJf8ri9r8nuXqZ2uLimvHOTkzj4&e=

________________________________________
From: spacewalk-list-***@redhat.com <spacewalk-list-***@redhat.com> on behalf of Michael Mraka <https://urldefense.proofpoint.com/v2/url?u=http-3A__michael.mraka-40redhat.com&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=ZV9A48T4fug2EDxquJwPgqYu5Hk7bzQs8mhd4rDoJxo&e= >
Sent: Wednesday, May 31, 2017 09:35
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

Fouts, Christopher:
> From that page,
>
> “Then reconfigure jabberd and restart the Satellite services”
>
> What (re)configuration does jabberd need?

Hi Chris,

try to look at
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_spacewalkproject_spacewalk_wiki_OsadHowTo&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=E-9ed2yJu3fClL1Fm74mtGyG8c6zylJ-N5YVaueNvyA&e=
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_spacewalkproject_spacewalk_wiki_JabberAndOSAD&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=5_tvcXZSOf4jtiGGn_sQCNsu5ElrFX48ipEQTHxqoIY&s=S8B3sT8rAh4g8YJ7LZHlTNLu9RmrhZ9phoY5CZTpDe0&e=

BTW in nightly version (upcomming 2.7) we've changed default jabberd backend from berkeleydb to sqlite which seems to be more reliable.

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

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

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

[Ree, Jan-Albert van]

The following blog should be all you need :
https://omg.dje.li/2017/03/configuring-spacewalks-jabberd-to-use-a-postgresql-backend/

--
Jan-Albert



Jan-Albert van Ree | Linux System Administrator | MARIN Support Group
MARIN | T [phone] | mailto:***@marin.nl | http://www.marin.nl

MARIN news: http://www.marin.nl/web/News/News-items/CRS-open-meeting-in-Cadiz-Spain-June-1-2.htm

________________________________________
From: spacewalk-list-***@redhat.com <spacewalk-list-***@redhat.com> on behalf of Wilkinson, Matthew <***@alliantenergy.com>
Sent: Wednesday, May 31, 2017 18:20
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

Can I ask how you configured jabber to use PostgreSQL?

[Wilkinson, Matthew]

Awesome thank you so much! I'm going to look into this. Does this cause any problems with upgrades from one minor version of Spacewalk to another? Or do the configs remain persistent and work after updates/upgrades?

--Matthew Wilkinson


-----Original Message-----
From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Ree, Jan-Albert van
Sent: Wednesday, May 31, 2017 12:17
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

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

**********************************************************************
The following blog should be all you need :
https://urldefense.proofpoint.com/v2/url?u=https-3A__omg.dje.li_2017_03_configuring-2Dspacewalks-2Djabberd-2Dto-2Duse-2Da-2Dpostgresql-2Dbackend_&d=DwICAg&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=EZ5UjOCV4paVA2WrByy0kojotVN-FO3EybQe3sP_wcE&s=7HH9kGRbZBRILFPdzwbq7t0Pvw5PBLEkwWNIk5jfd5Q&e=

--
Jan-Albert



Jan-Albert van Ree | Linux System Administrator | MARIN Support Group MARIN | T [phone] | mailto:***@marin.nl | https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marin.nl&d=DwICAg&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=EZ5UjOCV4paVA2WrByy0kojotVN-FO3EybQe3sP_wcE&s=JJvOS0-vXCYeK0R-FWXidEILa5zTwMi3Bj8ZE8h8YEQ&e=

MARIN news: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marin.nl_web_News_News-2Ditems_CRS-2Dopen-2Dmeeting-2Din-2DCadiz-2DSpain-2DJune-2D1-2D2.htm&d=DwICAg&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=EZ5UjOCV4paVA2WrByy0kojotVN-FO3EybQe3sP_wcE&s=K93acB6PX-BTzJzd-f_EGx0pzl52wPFl4bmlrZa1W3A&e=

________________________________________
From: spacewalk-list-***@redhat.com <spacewalk-list-***@redhat.com> on behalf of Wilkinson, Matthew <***@alliantenergy.com>
Sent: Wednesday, May 31, 2017 18:20
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

Can I ask how you configured jabber to use PostgreSQL?

[Avi Miller]

Hi,

> On 1 Jun 2017, at 3:58 am, Wilkinson, Matthew <***@alliantenergy.com> wrote:
>
> Awesome thank you so much! I'm going to look into this. Does this cause any problems with upgrades from one minor version of Spacewalk to another? Or do the configs remain persistent and work after updates/upgrades?

It does cause very minor problems: during the upgrade, when you re-run spacewalk-setup --upgrade, it’ll reset the config back to “db” (or “sqlite” in 2.7). It doesn’t retain the current setting, but it does retain the db-specific configuration. You’ll need to re-edit the two files and switch them back to pgsql before starting the Spacewalk services.

I keep meaning to either log an issue or fix this, but I always seem to have something else on my plate.

Cheers,
Avi

--
Oracle <http://www.oracle.com>
Avi Miller | Product Management Director | [phone]
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia

[Wilkinson, Matthew]

Ok thanks Avi. I read your blog post and was able to successfully configure jabberd to use postgres on my OL 6 box. However, I wasn't able to get it to work on an OL 7 box. I keep getting this in my syslog:

May 31 15:36:34 <hostnameredacted> jabberd/sm[21956]: pgsql: connection to database failed: could not connect to server: Permission denied#012#011Is the server running locally and accepting#012#011connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

Mind you, I can indeed connect using jabberd2 user via the psql command just fine.

No matter what I do to ensure the jabberd2 user has rights/grants and no matter what I do to allow the user to connect via the pg_hba.conf I can't get jabberd to start on OL 7 after configuring it for pgsql.

Did you get it working on OL 7?

--Matthew Wilkinson


-----Original Message-----
From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Avi Miller
Sent: Wednesday, May 31, 2017 15:02
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

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

**********************************************************************
Hi,

> On 1 Jun 2017, at 3:58 am, Wilkinson, Matthew <***@alliantenergy.com> wrote:
>
> Awesome thank you so much! I'm going to look into this. Does this cause any problems with upgrades from one minor version of Spacewalk to another? Or do the configs remain persistent and work after updates/upgrades?

It does cause very minor problems: during the upgrade, when you re-run spacewalk-setup --upgrade, it’ll reset the config back to “db” (or “sqlite” in 2.7). It doesn’t retain the current setting, but it does retain the db-specific configuration. You’ll need to re-edit the two files and switch them back to pgsql before starting the Spacewalk services.

I keep meaning to either log an issue or fix this, but I always seem to have something else on my plate.

Cheers,
Avi

--
Oracle <http://www.oracle.com>
Avi Miller | Product Management Director | [phone] Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia


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

[Avi Miller]

Hi,

> On 1 Jun 2017, at 6:40 am, Wilkinson, Matthew <***@alliantenergy.com> wrote:
>
> No matter what I do to ensure the jabberd2 user has rights/grants and no matter what I do to allow the user to connect via the pg_hba.conf I can't get jabberd to start on OL 7 after configuring it for pgsql.
> Did you get it working on OL 7?


Yes, the blog post was written on OL7. Can you email me your sm.xml and pg_hba.conf files directly so I can take a look at your configuration and compare it to mine? Also, if SElinux is enabled, see if disabling it resolves the issue.

Cheers,
Avi

P.S. I’m out of the office for the rest of the day, so I’ll probably only get a chance to look at any replies tomorrow.

--
Oracle <http://www.oracle.com>
Avi Miller | Product Management Director | [phone]
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia

[Wilkinson, Matthew]

OK I actually figured it out. It was indeed SELinux that was preventing jabber from connecting to the UNIX socket.
What's strange, though, is that the syslog never showed me the messages until I rebooted into Permissive mode.

After I did that, I got the SELinux warnings that sm and c2s were being prevented from "connectto" access to the unix_steam_socket on /run/postgresql/.s.PGSQL.5432

After I ran the suggested fix command:

setsebool -P daemons_enable_cluster_mode 1

And rebooted again back into enforcing mode, jabber was able to start using pgsql.

Thanks for the help all.

--Matthew Wilkinson


-----Original Message-----
From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Avi Miller
Sent: Wednesday, May 31, 2017 15:50
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

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

**********************************************************************
Hi,

> On 1 Jun 2017, at 6:40 am, Wilkinson, Matthew <***@alliantenergy.com> wrote:
>
> No matter what I do to ensure the jabberd2 user has rights/grants and no matter what I do to allow the user to connect via the pg_hba.conf I can't get jabberd to start on OL 7 after configuring it for pgsql.
> Did you get it working on OL 7?


Yes, the blog post was written on OL7. Can you email me your sm.xml and pg_hba.conf files directly so I can take a look at your configuration and compare it to mine? Also, if SElinux is enabled, see if disabling it resolves the issue.

Cheers,
Avi

P.S. I’m out of the office for the rest of the day, so I’ll probably only get a chance to look at any replies tomorrow.

--
Oracle <http://www.oracle.com>
Avi Miller | Product Management Director | [phone] Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia


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

[Michael Mraka]

Ree, Jan-Albert van:
> While I agree that sqlite is better than berkeleydb why not make PostgreSQL the default if the PostgreSQL database is already being set up during installation ( ie spacewalk-setup-postgresql is called )

We try to keep configuration unified accross different spacewalk variants.
And because jabberd can't connect to oracle we would need to configure
it with sqlite anyway in case of spacewalk with oracle backend.

If you want to try jabberd with postgresql backend see Avi's blog
https://omg.dje.li/2017/03/configuring-spacewalks-jabberd-to-use-a-postgresql-backend/


> Our modest installation (roughly 80 clients) still wasn't rock solid using sqlite (instead of crashing almost daily it became a 'once a month' thing where the DB got corrupted), only after moving to PostgreSQL do we now have an osa-dispatcher/jabber/osad setup which requires virtually no maintenance and is pretty much crash-proof.
>
> Regards,
> --
> Jan-Albert

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

[Ree, Jan-Albert van]

>

Jan-Albert van Ree | Linux System Administrator | MARIN Support Group
MARIN | T [phone] | mailto:***@marin.nl | http://www.marin.nl

MARIN news: http://www.marin.nl/web/News/News-items/Zeeen-zonder-zwavel-Het-Financieele-Dagblad.htm

-----Original Message-----
>
> Ree, Jan-Albert van:
> > While I agree that sqlite is better than berkeleydb why not make
> > PostgreSQL the default if the PostgreSQL database is already being
> set
> > up during installation ( ie spacewalk-setup-postgresql is called )

> We try to keep configuration unified accross different spacewalk
> variants.
> And because jabberd can't connect to oracle we would need to configure
> it with sqlite anyway in case of spacewalk with oracle backend.

Thats a good point, never thought about people still running Oracle...
Is it actually still being used a lot now that PostgreSQL is so mature?

> If you want to try jabberd with postgresql backend see Avi's blog
> https://omg.dje.li/2017/03/configuring-spacewalks-jabberd-to-use-a-
> postgresql-backend/

Can this information perhaps be added to the spacewalk wiki pages or at least a pointer be added in the wiki?
I'd be happy to assist in this if needed, but I think it's a shame these gems of information are not easily found.
--
Jan-Albert

[Wilkinson, Matthew]

Good idea. I actually edited the Spacewalk Wiki a long while ago regarding some BerkeleyDB tips and tricks I had discovered. But they moved the Wiki to Github so I'm not sure how that works any longer...

--Matthew Wilkinson


-----Original Message-----
From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Ree, Jan-Albert van
Sent: Thursday, June 01, 2017 04:17
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

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

**********************************************************************
>

Jan-Albert van Ree | Linux System Administrator | MARIN Support Group MARIN | T [phone] | mailto:***@marin.nl | https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marin.nl&d=DwICAg&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=ULAoBqalMYiaV0U8MmMZFn7HOX_GttjvRoFzVH-vGS0&s=COLwUGxwkAjv-C289mDjvneE0Ti1uzPIAMp0Q4n07Kw&e=

MARIN news: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.marin.nl_web_News_News-2Ditems_Zeeen-2Dzonder-2Dzwavel-2DHet-2DFinancieele-2DDagblad.htm&d=DwICAg&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=ULAoBqalMYiaV0U8MmMZFn7HOX_GttjvRoFzVH-vGS0&s=cbnK22w6ORCSXLPrXVyR4Buj60lMUMbwEqzafgOJFmc&e=

-----Original Message-----
>
> Ree, Jan-Albert van:
> > While I agree that sqlite is better than berkeleydb why not make
> > PostgreSQL the default if the PostgreSQL database is already being
> set
> > up during installation ( ie spacewalk-setup-postgresql is called )

> We try to keep configuration unified accross different spacewalk
> variants.
> And because jabberd can't connect to oracle we would need to configure
> it with sqlite anyway in case of spacewalk with oracle backend.

Thats a good point, never thought about people still running Oracle...
Is it actually still being used a lot now that PostgreSQL is so mature?

> If you want to try jabberd with postgresql backend see Avi's blog
> https://urldefense.proofpoint.com/v2/url?u=https-3A__omg.dje.li_2017_0
> 3_configuring-2Dspacewalks-2Djabberd-2Dto-2Duse-2Da-2D&d=DwICAg&c=GUDV
> eAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQ
> nlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=ULAoBqalMYiaV0U8MmMZFn7HOX_Gttj
> vRoFzVH-vGS0&s=OoWQnzVyD5GolOyrug4NA_7SYFhVzMb2NPVI1mdEFu4&e=
> postgresql-backend/

Can this information perhaps be added to the spacewalk wiki pages or at least a pointer be added in the wiki?
I'd be happy to assist in this if needed, but I think it's a shame these gems of information are not easily found.
--
Jan-Albert

[Michael Mraka]

> > > While I agree that sqlite is better than berkeleydb why not make
> > > PostgreSQL the default if the PostgreSQL database is already being set
> > > up during installation ( ie spacewalk-setup-postgresql is called )
>
> > We try to keep configuration unified accross different spacewalk
> > variants.
> > And because jabberd can't connect to oracle we would need to configure
> > it with sqlite anyway in case of spacewalk with oracle backend.
>
> Thats a good point, never thought about people still running Oracle...
> Is it actually still being used a lot now that PostgreSQL is so mature?
>
> > If you want to try jabberd with postgresql backend see Avi's blog
> > https://omg.dje.li/2017/03/configuring-spacewalks-jabberd-to-use-a-
> > postgresql-backend/
>
> Can this information perhaps be added to the spacewalk wiki pages or at least a pointer be added in the wiki?

Fair enough. I've added the links to
https://github.com/spacewalkproject/spacewalk/wiki/OsadHowTo

> I'd be happy to assist in this if needed, but I think it's a shame these gems of information are not easily found.
> --
> Jan-Albert

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

[Wilkinson, Matthew]

Thanks Michael.

--Matthew Wilkinson


-----Original Message-----
From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Michael Mraka
Sent: Friday, June 02, 2017 04:21
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

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

**********************************************************************
> > > While I agree that sqlite is better than berkeleydb why not make
> > > PostgreSQL the default if the PostgreSQL database is already being
> > > set up during installation ( ie spacewalk-setup-postgresql is
> > > called )
>
> > We try to keep configuration unified accross different spacewalk
> > variants.
> > And because jabberd can't connect to oracle we would need to
> > configure it with sqlite anyway in case of spacewalk with oracle backend.
>
> Thats a good point, never thought about people still running Oracle...
> Is it actually still being used a lot now that PostgreSQL is so mature?
>
> > If you want to try jabberd with postgresql backend see Avi's blog
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__omg.dje.li_2017
> > _03_configuring-2Dspacewalks-2Djabberd-2Dto-2Duse-2Da-2D&d=DwIGaQ&c=
> > GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805q
> > sHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=MPKGPZWpV0jYhtloDTEJIsu
> > wzW7t1vE2Wgbg_Kqr-Ic&s=ewUHRXnqcrW8rFd72vsz9p5Be65Hs9SqmFaH-pBpeuE&e
> > =
> > postgresql-backend/
>
> Can this information perhaps be added to the spacewalk wiki pages or at least a pointer be added in the wiki?

Fair enough. I've added the links to
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_spacewalkproject_spacewalk_wiki_OsadHowTo&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=MPKGPZWpV0jYhtloDTEJIsuwzW7t1vE2Wgbg_Kqr-Ic&s=AOCq68C-2liV1fw8QBU9rapoBB-YolLpHbqPPvzRuiY&e=

> I'd be happy to assist in this if needed, but I think it's a shame these gems of information are not easily found.
> --
> Jan-Albert

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

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

[Wilkinson, Matthew]

Good call. Thanks Michael. I have been configuring my Spacewalk instances with PostgreSQL and it's working well so I agree with Jan-Albert that it'd be nice to have the official Spacewalk documentation updated with the DB options and configs for using Postgres.

--Matthew Wilkinson


-----Original Message-----
From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Michael Mraka
Sent: Thursday, June 01, 2017 03:41
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

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

**********************************************************************
Ree, Jan-Albert van:
> While I agree that sqlite is better than berkeleydb why not make
> PostgreSQL the default if the PostgreSQL database is already being set
> up during installation ( ie spacewalk-setup-postgresql is called )

We try to keep configuration unified accross different spacewalk variants.
And because jabberd can't connect to oracle we would need to configure it with sqlite anyway in case of spacewalk with oracle backend.

If you want to try jabberd with postgresql backend see Avi's blog https://urldefense.proofpoint.com/v2/url?u=https-3A__omg.dje.li_2017_03_configuring-2Dspacewalks-2Djabberd-2Dto-2Duse-2Da-2Dpostgresql-2Dbackend_&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=VpK_HJV5w79miGmmoWw-Di5ULIgMMmIkW7JWZLrUctI&s=pCbYSthwAo2SGk-gle2dZoAwXrKOelWZxjmkvQUL4tM&e=


> Our modest installation (roughly 80 clients) still wasn't rock solid using sqlite (instead of crashing almost daily it became a 'once a month' thing where the DB got corrupted), only after moving to PostgreSQL do we now have an osa-dispatcher/jabber/osad setup which requires virtually no maintenance and is pretty much crash-proof.
>
> Regards,
> --
> Jan-Albert

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

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

[Rob Sterenborg]

To be honest, I would also like it if a Spacewalk upgrade (say, from 2.6 to 2.7 somewhere in the future) would not touch current configuration. So that if I configure PostgreSQL it will not revert to sqlite or so. (Unless of course it really some changes to keep things working.) It's not that I can't reconfigure, but it can take you off-guard.


--
Rob


> -----Original Message-----
> From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-
> ***@redhat.com] On Behalf Of Wilkinson, Matthew
> Sent: donderdag 1 juni 2017 15:32
> To: spacewalk-***@redhat.com
> Subject: Re: [Spacewalk-list] Error connecting to jabber
>
> Good call. Thanks Michael. I have been configuring my Spacewalk instances
> with PostgreSQL and it's working well so I agree with Jan-Albert that it'd
> be nice to have the official Spacewalk documentation updated with the DB
> options and configs for using Postgres.
>
> --Matthew Wilkinson
>
>
> -----Original Message-----
> From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-
> ***@redhat.com] On Behalf Of Michael Mraka
> Sent: Thursday, June 01, 2017 03:41
> To: spacewalk-***@redhat.com
> Subject: Re: [Spacewalk-list] Error connecting to jabber
>
> [This is an external email. Be cautious with links, attachments and
> responses.]
>
> **********************************************************************
> Ree, Jan-Albert van:
> > While I agree that sqlite is better than berkeleydb why not make
> > PostgreSQL the default if the PostgreSQL database is already being set
> > up during installation ( ie spacewalk-setup-postgresql is called )
>
> We try to keep configuration unified accross different spacewalk variants.
> And because jabberd can't connect to oracle we would need to configure it
> with sqlite anyway in case of spacewalk with oracle backend.
>
> If you want to try jabberd with postgresql backend see Avi's blog
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__omg.dje.li_2017_03_configuring-2Dspacewalks-2Djabberd-2Dto-2Duse-2Da-
> 2Dpostgresql-
> 2Dbackend_&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yy
> n0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-
> Tq1kdA&m=VpK_HJV5w79miGmmoWw-Di5ULIgMMmIkW7JWZLrUctI&s=pCbYSthwAo2SGk-
> gle2dZoAwXrKOelWZxjmkvQUL4tM&e=
>
>
> > Our modest installation (roughly 80 clients) still wasn't rock solid using
> sqlite (instead of crashing almost daily it became a 'once a month' thing
> where the DB got corrupted), only after moving to PostgreSQL do we now have
> an osa-dispatcher/jabber/osad setup which requires virtually no maintenance
> and is pretty much crash-proof.
> >
> > Regards,
> > --
> > Jan-Albert
>
> Regards,
>
> --
> Michael Mráka
> System Management Engineering, Red Hat
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-***@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-***@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list

[Avi Miller]

Hi,

> On 1 Jun 2017, at 6:40 pm, Michael Mraka <***@redhat.com> wrote:
>
> And because jabberd can't connect to oracle we would need to configure
> it with sqlite anyway in case of spacewalk with oracle backend.


This is something we’re hoping to address soon, i.e. bring Oracle support back to jabberd. If I manage to get some resources allocated to this and we get it working again, our next step would be to automatically configure jabberd to use whichever DB backend Spacewalk is using.

I’ll let you know if/when this happens, though. :)

Cheers,
Avi

--
Oracle <http://www.oracle.com>
Avi Miller | Product Management Director | [phone]
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia

[Wilkinson, Matthew]

Avi,

Can you add a section on your blog post about configuring Jabber for Postgres about SELinux? I had to enter this command to allow jabber sm and c2s to connect to Postgres:

setsebool -P daemons_enable_cluster_mode 1

Thanks,

--Matthew Wilkinson


-----Original Message-----
From: spacewalk-list-***@redhat.com [mailto:spacewalk-list-***@redhat.com] On Behalf Of Avi Miller
Sent: Thursday, June 01, 2017 15:16
To: spacewalk-***@redhat.com
Subject: Re: [Spacewalk-list] Error connecting to jabber

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

**********************************************************************
Hi,

> On 1 Jun 2017, at 6:40 pm, Michael Mraka <https://urldefense.proofpoint.com/v2/url?u=http-3A__michael.mraka-40redhat.com&d=DwIGaQ&c=GUDVeAVg1gjs_GJkmwL1m3gEzDND7NeJG5BIAX_2yRE&r=zxSMv3Yyn0u8GiLjBm805qsHQ-PQnlWklaJFaNwJsRdou0Rx32Ld6bt57-Tq1kdA&m=JwdIkff-kbQNJ5LnM9Jv9x_yhTj4OODUyjJ4VJhsDHQ&s=zPnFqk7zPllRbFIcHPbWrNPNw7_ADVgQHYwsBs4qlkE&e= > wrote:
>
> And because jabberd can't connect to oracle we would need to configure
> it with sqlite anyway in case of spacewalk with oracle backend.


This is something we’re hoping to address soon, i.e. bring Oracle support back to jabberd. If I manage to get some resources allocated to this and we get it working again, our next step would be to automatically configure jabberd to use whichever DB backend Spacewalk is using.

I’ll let you know if/when this happens, though. :)

Cheers,
Avi

--
Oracle <http://www.oracle.com>
Avi Miller | Product Management Director | [phone] Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia

[Avi Miller]

Hi,

> On 2 Jun 2017, at 11:04 pm, Wilkinson, Matthew <***@alliantenergy.com> wrote:
>
> Can you add a section on your blog post about configuring Jabber for Postgres about SELinux? I had to enter this command to allow jabber sm and c2s to connect to Postgres:


Certainly can, thanks for the feedback. :)

Cheers,
Avi

--
Oracle <http://www.oracle.com>
Avi Miller | Product Management Director | [phone]
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia

[Fouts, Christopher]

Step 4 on https://github.com/spacewalkproject/spacewalk/wiki/JabberAndOSAD says “4. Within /etc/jabberd/server.pem, verify that the same FQDN is present here.” However my server.pem file doesn’t have FQDN section, only the BEGIN/END PRIVATE KEY and BEGIN/END CERTIFICATE parts. Are the instructions outdated? If not, how do I re-generate my server.pem file?

Chris

On 5/31/17, 3:35 AM, "spacewalk-list-***@redhat.com on behalf of Michael Mraka" <spacewalk-list-***@redhat.com on behalf of ***@redhat.com> wrote:

Fouts, Christopher:
> From that page,
>
> “Then reconfigure jabberd and restart the Satellite services”
>
> What (re)configuration does jabberd need?

Hi Chris,

try to look at
https://github.com/spacewalkproject/spacewalk/wiki/OsadHowTo
https://github.com/spacewalkproject/spacewalk/wiki/JabberAndOSAD

BTW in nightly version (upcomming 2.7) we've changed default jabberd
backend from berkeleydb to sqlite which seems to be more reliable.

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

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

[Fouts, Christopher]

I fixed it. Turns out I had to use the /etc/pki/spacewalk/jabberd/server.pem instead of /etc/jabberd/server.pem file.

Chris



On 5/31/17, 3:35 AM, "spacewalk-list-***@redhat.com on behalf of Michael Mraka" <spacewalk-list-***@redhat.com on behalf of ***@redhat.com> wrote:

Fouts, Christopher:
> From that page,
>
> “Then reconfigure jabberd and restart the Satellite services”
>
> What (re)configuration does jabberd need?

Hi Chris,

try to look at
https://github.com/spacewalkproject/spacewalk/wiki/OsadHowTo
https://github.com/spacewalkproject/spacewalk/wiki/JabberAndOSAD

BTW in nightly version (upcomming 2.7) we've changed default jabberd
backend from berkeleydb to sqlite which seems to be more reliable.

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

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

[Robert Paschedag]

Am 22. Mai 2017 23:17:15 MESZ schrieb InvalidPath <***@gmail.com>:
>Hey everyone. Another person here having the whole can't connect to
>jabber
>server issue.
>
>I've gone through the verifying of hostname, hosts, resolv, etc files.
>I've ran the spacewalk-hostname-rename binary.
>
>***@automation:/usr/bin$ /usr/sbin/spacewalk-service status
>
>Redirecting to /bin/systemctl status postgresql.service
>
>● postgresql.service - PostgreSQL database server
>
> Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled;
>vendor preset: disabled)
> Active: active (running) since Mon 2017-05-22 14:52:07 MDT; 44s ago
> Process: 15302 ExecStop=/usr/bin/pg_ctl stop -D ${PGDATA} -s -m fast
>(code=exited, status=0/SUCCESS)
> Process: 15331 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p
>${PGPORT} -w -t 300 (code=exited, status
>=0/SUCCESS)
> Process: 15325 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA}
>(code=exited, status=0/SUCCESS)
>Main PID: 15334 (postgres)
> CGroup: /system.slice/postgresql.service
> ├─15334 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
> ├─15335 postgres: logger process
> ├─15337 postgres: checkpointer process
> ├─15338 postgres: writer process
> ├─15339 postgres: wal writer process
> ├─15340 postgres: autovacuum launcher process
> ├─15341 postgres: stats collector process
> ├─15449 postgres: rhnuser rhnschema 127.0.0.1(50548) idle
> ├─15450 postgres: rhnuser rhnschema 127.0.0.1(50549) idle
> ├─15451 postgres: rhnuser rhnschema 127.0.0.1(50552) idle
> ├─15452 postgres: rhnuser rhnschema 127.0.0.1(50554) idle
> ├─15453 postgres: rhnuser rhnschema 127.0.0.1(50556) idle
> ├─15737 postgres: rhnuser rhnschema 127.0.0.1(50560) idle
> ├─15738 postgres: rhnuser rhnschema 127.0.0.1(50563) idle
> ├─15739 postgres: rhnuser rhnschema 127.0.0.1(50562) idle
> ├─15740 postgres: rhnuser rhnschema 127.0.0.1(50566) idle
> ├─15741 postgres: rhnuser rhnschema 127.0.0.1(50568) idle
> ├─15742 postgres: rhnuser rhnschema 127.0.0.1(50570) idle
> ├─15743 postgres: rhnuser rhnschema 127.0.0.1(50572) idle
> ├─15744 postgres: rhnuser rhnschema 127.0.0.1(50574) idle
> ├─15745 postgres: rhnuser rhnschema 127.0.0.1(50576) idle
> ├─15781 postgres: rhnuser rhnschema 127.0.0.1(50580) idle
> ├─15828 postgres: rhnuser rhnschema 127.0.0.1(50582) idle
> ├─15829 postgres: rhnuser rhnschema 127.0.0.1(50584) idle
> ├─15830 postgres: rhnuser rhnschema 127.0.0.1(50586) idle
> ├─15831 postgres: rhnuser rhnschema 127.0.0.1(50588) idle
> ├─15832 postgres: rhnuser rhnschema 127.0.0.1(50590) idle
> ├─15835 postgres: rhnuser rhnschema 127.0.0.1(50592) idle
> ├─15841 postgres: rhnuser rhnschema 127.0.0.1(50606) idle
> ├─15842 postgres: rhnuser rhnschema 127.0.0.1(50608) idle
> └─15844 postgres: rhnuser rhnschema 127.0.0.1(50612) idle
>
>May 22 14:52:06 automation.egovmt.com systemd[1]: Starting PostgreSQL
>database server...
>May 22 14:52:07 automation.egovmt.com systemd[1]: Started PostgreSQL
>database server.
>Redirecting to /bin/systemctl status jabberd.service
>● jabberd.service - Jabber Server
>Loaded: loaded (/usr/lib/systemd/system/jabberd.service; enabled;
>vendor
>preset: disabled)
> Active: inactive (dead) since Mon 2017-05-22 14:52:07 MDT; 44s ago
> Process: 15362 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
>Main PID: 15362 (code=exited, status=0/SUCCESS)
>
>May 22 14:52:07 automation.egovmt.com systemd[1]: Starting Jabber
>Server...
>May 22 14:52:07 automation.egovmt.com systemd[1]: Started Jabber
>Server.
>May 22 14:52:07 automation.egovmt.com systemd[1]: Stopped Jabber
>Server.
>May 22 14:52:07 automation.egovmt.com systemd[1]: Stopping Jabber
>Server...
>Redirecting to /bin/systemctl status tomcat.service
>● tomcat.service - Apache Tomcat Web Application Container
>Loaded: loaded (/usr/lib/systemd/system/tomcat.service; enabled; vendor
>preset: disabled)
> Active: active (running) since Mon 2017-05-22 14:52:07 MDT; 44s ago
>Main PID: 15381 (java)
> CGroup: /system.slice/tomcat.service
> └─15381 /usr/lib/jvm/jre/bin/java -ea -Xms256m -Xmx256m
>-Djava.awt.headless=true -Dorg.xml.sax.dr...
>
>May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017
>2:52:34
>PM org.apache.catalina.startup....tor
>May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Deployment
>of
>configuration descriptor /etc/to... ms
>May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017
>2:52:34
>PM org.apache.coyote.AbstractPr...art
>May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Starting
>ProtocolHandler ["http-bio-127.0.0.1-8080"]
>May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017
>2:52:34
>PM org.apache.coyote.AbstractPr...art
>May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Starting
>ProtocolHandler ["ajp-bio-127.0.0.1-8009"]
>May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017
>2:52:34
>PM org.apache.coyote.AbstractPr...art
>May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Starting
>ProtocolHandler ["ajp-bio-0:0:0:0:0:0...9"]
>May 22 14:52:34 automation.egovmt.com server[15381]: May 22, 2017
>2:52:34
>PM org.apache.catalina.startup....art
>May 22 14:52:34 automation.egovmt.com server[15381]: INFO: Server
>startup
>in 26364 ms
>Hint: Some lines were ellipsized, use -l to show in full.
>Redirecting to /bin/systemctl status httpd.service
>● httpd.service - The Apache HTTP Server
> Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor
>preset: disabled)
> Active: active (running) since Mon 2017-05-22 14:52:34 MDT; 16s ago
> Docs: man:httpd(8)
> man:apachectl(8)
> Process: 15127 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited,
>status=0/SUCCESS)
>Main PID: 15538 (httpd)
>Status: "Total requests: 7; Current requests/sec: 0.778; Current
>traffic:
>568 B/sec"
> CGroup: /system.slice/httpd.service
> ├─15538 /usr/sbin/httpd -DFOREGROUND
> ├─15539 /usr/sbin/httpd -DFOREGROUND
> ├─15540 /usr/sbin/httpd -DFOREGROUND
> ├─15541 /usr/sbin/httpd -DFOREGROUND
> ├─15542 /usr/sbin/httpd -DFOREGROUND
> ├─15543 /usr/sbin/httpd -DFOREGROUND
> ├─15544 /usr/sbin/httpd -DFOREGROUND
> ├─15545 /usr/sbin/httpd -DFOREGROUND
> └─15546 /usr/sbin/httpd -DFOREGROUND
>
>May 22 14:52:34 automation.egovmt.com systemd[1]: Starting The Apache
>HTTP
>Server...
>May 22 14:52:34 automation.egovmt.com systemd[1]: Started The Apache
>HTTP
>Server.
>Redirecting to /bin/systemctl status osa-dispatcher.service
>● osa-dispatcher.service - OSA Dispatcher daemon
>Loaded: loaded (/usr/lib/systemd/system/osa-dispatcher.service;
>enabled;
>vendor preset: disabled)
>Active: failed (Result: exit-code) since Mon 2017-05-22 14:52:35 MDT;
>16s
>ago
> Process: 15564 ExecStart=/usr/sbin/osa-dispatcher --pid-file
>/var/run/osa-dispatcher.pid (code=exited, status
>=255)
>
>
> Process: 15562 ExecStartPre=/bin/rm -f /var/run/osa-dispatcher.pid
>(code=exited, status=0/SUCCESS)
>Main PID: 2051 (code=killed, signal=TERM)
>
>May 22 14:52:34 automation.egovmt.com systemd[1]: Starting OSA
>Dispatcher
>daemon...
>May 22 14:52:35 automation.egovmt.com osa-dispatcher[15564]: Spacewalk
>15564 2017/05/22 14:52:35 -06:00: (...,)
>May 22 14:52:35 automation.egovmt.com osa-dispatcher[15564]: Spacewalk
>15564 2017/05/22 14:52:35 -06:00: (...,)
>May 22 14:52:35 automation.egovmt.com osa-dispatcher[15564]: ERROR:
>unhandled exception occurred: (unicode...).
>May 22 14:52:35 automation.egovmt.com systemd[1]:
>osa-dispatcher.service:
>control process exited, code=e...=255
>May 22 14:52:35 automation.egovmt.com systemd[1]: Failed to start OSA
>Dispatcher daemon.
>May 22 14:52:35 automation.egovmt.com systemd[1]: Unit
>osa-dispatcher.service entered failed state.
>May 22 14:52:35 automation.egovmt.com systemd[1]:
>osa-dispatcher.service
>failed.
>Hint: Some lines were ellipsized, use -l to show in full.
>Redirecting to /bin/systemctl status rhn-search.service
>● rhn-search.service - Spacewalk search engine
> Loaded: loaded (/usr/lib/systemd/system/rhn-search.service; enabled;
>vendor preset: disabled)
> Active: active (running) since Mon 2017-05-22 14:52:35 MDT; 16s ago
> Process: 15043 ExecStop=/usr/sbin/rhn-search stop (code=exited,
>status=0/SUCCESS)
> Process: 15583 ExecStart=/usr/sbin/rhn-search start (code=exited,
>status=0/SUCCESS)
>Main PID: 15596 (rhnsearchd)
> CGroup: /system.slice/rhn-search.service
> ├─15596 /usr/bin/rhnsearchd
>/usr/share/rhn/config-defaults/rhn_search_daemon.conf
>wrapper.pidfile...
> └─15598 /usr/bin/java
>-Djava.library.path=/usr/lib:/usr/lib64:/usr/lib/oracle/11.2/client/lib:/us...
>
>
>May 22 14:52:35 automation.egovmt.com systemd[1]: Starting Spacewalk
>search
>engine...
>May 22 14:52:35 automation.egovmt.com rhn-search[15583]: Starting
>rhn-search...
>May 22 14:52:35 automation.egovmt.com systemd[1]: Started Spacewalk
>search
>engine.
>● cobblerd.service - LSB: daemon for libvirt virtualization API
>Loaded: loaded (/etc/rc.d/init.d/cobblerd; bad; vendor preset:
>disabled)
> Active: active (running) since Mon 2017-05-22 14:52:36 MDT; 15s ago
> Docs: man:systemd-sysv-generator(8)
> Process: 15017 ExecStop=/etc/rc.d/init.d/cobblerd stop (code=exited,
>status=0/SUCCESS)
> Process: 15639 ExecStart=/etc/rc.d/init.d/cobblerd start (code=exited,
>status=0/SUCCESS)
> CGroup: /system.slice/cobblerd.service
> └─15649 /usr/bin/python -s /bin/cobblerd --daemonize
>
>May 22 14:52:35 automation.egovmt.com systemd[1]: Starting LSB: daemon
>for
>libvirt virtualization API...
>May 22 14:52:36 automation.egovmt.com cobblerd[15639]: Starting cobbler
>daemon: [ OK ]
>May 22 14:52:36 automation.egovmt.com systemd[1]: Started LSB: daemon
>for
>libvirt virtualization API.
>Redirecting to /bin/systemctl status taskomatic.service
>● taskomatic.service - Taskomatic
> Loaded: loaded (/usr/lib/systemd/system/taskomatic.service; enabled;
>vendor preset: disabled)
> Active: active (running) since Mon 2017-05-22 14:52:36 MDT; 14s ago
> Process: 14942 ExecStop=/usr/sbin/taskomatic stop (code=exited,
>status=0/SUCCESS)
> Process: 15677 ExecStart=/usr/sbin/taskomatic start (code=exited,
>status=0/SUCCESS)
>Main PID: 15691 (taskomaticd)
> CGroup: /system.slice/taskomatic.service
> ├─15691 /usr/bin/taskomaticd
>/usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf wrapper.pi...
> └─15746 /usr/bin/java -Dibm.dst.compatibility=true
>-Dfile.encoding=UTF-8 -Xms256m -Xmx1024m -Djav...
>
>May 22 14:52:36 automation.egovmt.com systemd[1]: Starting
>Taskomatic...
>May 22 14:52:36 automation.egovmt.com taskomatic[15677]: Starting RHN
>Taskomatic...
>May 22 14:52:36 automation.egovmt.com wrapper[15691]: --> Wrapper
>Started
>as Daemon
>May 22 14:52:36 automation.egovmt.com wrapper[15691]: Launching a
>JVM...
>May 22 14:52:36 automation.egovmt.com systemd[1]: Started Taskomatic.
>
>
>***@automation:/usr/sbin$ ./osa-dispatcher
>
>Spacewalk 15975 2017/05/22 14:53:07 -06:00: ('Error connecting to
>jabber
>server: Unable to connect to the host
>and port specified. See https://access.redhat.com/solutions/327903 for
>more
>information. ',)
>Spacewalk 15975 2017/05/22 14:53:07 -06:00: ('Error caught:',)
>
>
>
>ERROR: unhandled exception occurred: (unicode argument expected, got
>'str').
>***@automation:/usr/sbin$ ***@automation:/usr/sbin$ ./osa-dispatcher
>
>Spacewalk 15975 2017/05/22 14:53:07 -06:00: ('Error connecting to
>jabber
>server: Unable to connect to the host
>and port specified. See https://access.redhat.com/solutions/327903 for
>more
>information. ',)
>Spacewalk 15975 2017/05/22 14:53:07 -06:00: ('Error caught:',)
>
>
>
>ERROR: unhandled exception occurred: (unicode argument expected, got
>'str').
>***@automation:/usr/sbin$ semanage permissive -a osad_t
>
>
>
>Hopefully someone here can point me in the right direction.
>
>Thanks!!

In the jabber service definition...

ExecStart=/bin/true ???

Does not look right to me

Regards
Robert