On 09/11/05 14:39, Taymour A. El Erian wrote:
[...]
I used the config u sent me now am getting this error in my log.
am using SEMS 0.9.0 and I have no idea what these errors mean
Sep 11 14:33:30 serry /usr/sbin/openser[20658]: ERROR: fifo_t_reply:
lookup failed
Sep 11 14:33:30 serry /usr/sbin/openser[20658]: ERROR: fifo_server:
command (t_reply) processing failed
Sep 11 14:33:30 serry Sems[19839]: Error: (AmRequest.cpp)(reply)(368):
AmRequestUAS::reply: 481 fifo_t_reply: no such transaction
Sep 11 14:33:30 serry Sems[19839]: Error: (AmSession.cpp)(run)(217): 500
could not send response.
Did you get around this problem? The log messages say that sems tries
to send a reply to a transaction that does not exists in openser. This
can be due late reply (the transaction expired) bad parameters sent
over fifo from sems to openser.
Would help a network trace for such situation (using ngrep or
ethereal). Also, you can increase the debug level in openser and sems,
to get more messages.
Daniel
I did not get around it, It is definitely not a network problem since
sems and openser are on the same machine