My guess is that your postgresql 9.3 instance is not using the
configuration generated by spacewalk-setup-postgresql. In particular, I
suspect this problem would be fixed by setting "bytea_output = 'escape'"
in postgresql.conf. Try appending the following to postgresql.conf and
restarting the db:
### spacewalk-setup-postgresql modified values
checkpoint_completion_target = 0.7
checkpoint_segments = 8
effective_cache_size = 1152MB
log_line_prefix = '%m '
maintenance_work_mem = 96MB
max_connections = 600
shared_buffers = 384MB
wal_buffers = 4MB
work_mem = 2560kB
bytea_output = 'escape'
-Stephen
On 07/18/2014 10:26 AM, Andy Ingham wrote:
For the most part, things look good and all functionality seems to be
happy after my postgres upgrade EXCEPT this one interesting issue:
The running of a "remote command" FUNCTIONS correctly, however, the output
in the webUI when one visits [System name] > Events > History > "Run an
arbitrary script scheduled by XXXX"
no longer shows the command / script that was run, but rather displays a
hex string like:
x23212f62696e2f73680a73657276696365206175746f66732072657374617274
Likewise, the "output" (whether raw or filtered) displays as hex, rather
than as something useful / readable.
Sure seems that the data in the postgres db is now being stored in a new
format or with a new data type.
Anyone seen anything like this or have ideas about why I'm seeing this?
Best wishes,
Andy
Andy Ingham
IT Infrastructure
Fuqua School of Business
Duke University
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
