-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sorry if I'm missing something, but is the PUM side configured to use
SSLized syslog? What does the LAN trace show? For example, if PUM were
trying to send normal-syslog-ish and Sentinel were listening hoping for an
SSLized connection this would fail as you described.
Good luck.
TommieFrancis wrote:
> Hi,
>
> I have a Sentinel 6.1 RD (hotfix loaded) box set up with 2 collectors
> running. SLES 10 collector using a syslog connector and Privileged User
> Management collecctor also using syslog connector.
>
> Syslog for SLES 10 is setup to listen on TCP port1514, events coming in
> and no issues. I followed the documentation on the PUM collector, but I
> have RD listen on Open SSL port number 514.
>
> Issue 1: TCP port 514 is already in use by a JAVA process.
> Issue 2: When changing the port to listen on for PUM to Open SSL and
> port 1515 for example, the connection from PUM to Sentinel is made but
> lost immedialty, thus the eventsource is displayed in ESM but connection
> to the event source (PUM) is lost again. when events are actually
> getting through to Sentinel it shows as Unsupported Events, which does
> not really help.
>
> Any one experienced this before?
>
> P.S. the syslog connector version is r6.5, as I am unable to import
> r6.7 as per other thread... :-)
>
> Thanks
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJKz0E0AAoJEF+XTK08PnB5XeYQAJrroDaczm N7T3GCe/8v5n96
f5pUOKtrVMU7paHpkhTcuB/wQ3nzzHOsXYRYJ+2C43XAwE4j+tNk8MXuBI5i2RHt
nEOKBryEdlQFYKXQNyCsRGI2J2Yx33JKwrSWj0EDpcL3osh4aL evY7l2WbYEmcEC
SSAKMF32KS11+F4I4XJGQdL1p+TBzZtL693sfjneVouB9lJp8X 7bC/Xj27s/mIlU
DgSi9tgbzxqOahXVGgqMP35mc+pcBuCOP9+SdTSk9MTg21MLtw ww1Trt9GFOgtiy
mOACzBrOe5Gzsyqi3NFytR+yx/mDwVby4wwLMpMYu21luTEeI8DrdVSyOjCd2///
dg73CSa9rh4oTpoX4f32/Y/cJ+sDRzXJizhU1nIMXnZrIWkZkTavhl2F8HG99DEu
DqYXTnQxXvjqMdGPfvdYmtn228eSYcNrPvH5Q8OZd18x2CCLDZ/ZebOXkUCpni/s
zT2rJk3PSwRMWJaqFlnSutxsKCTwpObupN3qHheiB2v8HUFqCS SO1qCBIDUfDR8d
pC3biWA/lJ1p+Bme8rvlcF/Pq9R9P+YDtJ53oLMfAvnQMgabjEUhqLOj3OSmejvv
8g/v9HC/4+vzlgCHf1/gOQTuOG8D77JkjUY9gH3lMnVkZIVu0L801k017VXuRxuj
tX9y2yjcwoPJOtGWtKl4
=Kh4v
-----END PGP SIGNATURE-----
Re: PUM Collector
Threaded Mode
