Is there a way to stop the last member of a queue from pausing or logging out of the queue?

Udo

Any news on this issue? We got no reply for over a week now.

Hi, it's runnung on Debian Lenny 2.6.26-2-686 Kernel, 32 bit.

Another crash:

STATUS channel DAHDI/32-1 already in memory, ignoring state
Use of uninitialized value in string ne at script/fop2_server.pl line 2268.

SET LINK DAHDI/32-1 to DAHDI/1-1

** MAIN End of block from localhost

127.0.0.1       <- Event: Status
127.0.0.1       <- Privilege: Call
127.0.0.1       <- Channel: DAHDI/1-1
127.0.0.1       <- CallerIDNum: XXXXXXXXX
127.0.0.1       <- CallerIDName:
127.0.0.1       <- Accountcode:
127.0.0.1       <- ChannelState: 6
127.0.0.1       <- ChannelStateDesc: Up
127.0.0.1       <- Context: to-system
127.0.0.1       <- Extension: XXXXXXXXXX
127.0.0.1       <- Priority: 6
127.0.0.1       <- Seconds: 39
127.0.0.1       <- BridgedChannel: DAHDI/32-1
127.0.0.1       <- BridgedUniqueid: asterisk-dt-1282907862.29687
127.0.0.1       <- Uniqueid: asterisk-dt-1282907862.29686
127.0.0.1       <- Server: 0

** MAIN AMI event received...
** MAIN There's an 'Event' in the event block
** MAIN Event detected block_count = 0
** MAIN There are 0 blocks for processing
** MAIN Answer block cleared

** PROCESA_BLOQUE STATUS 0
Use of uninitialized value in string ne at script/fop2_server.pl line 2207.

It's a HASH, not blessed.
Can't call method "setUnique" on unblessed reference at script/fop2_server.pl line 2235.

Crash ...

It was running all night till noon with -X 15 w/o any crash. Now suddenly it crashes every minute.
XXXing out numbers for privacy reasons. Running with -X 255:

127.0.0.1       <- Event: Status
127.0.0.1       <- Privilege: Call
127.0.0.1       <- Channel: DAHDI/4-1
127.0.0.1       <- CallerIDNum: XXXXXXX
127.0.0.1       <- CallerIDName: <unknown>
127.0.0.1       <- Account:
127.0.0.1       <- State: Up
127.0.0.1       <- BridgedChannel: DAHDI/56-1
127.0.0.1       <- BridgedUniqueid: asterisk-dt-1282907397.29645
127.0.0.1       <- Uniqueid: asterisk-dt-1282907401.29647
127.0.0.1       <- Server: 0

** MAIN AMI event received...
** MAIN There's an 'Event' in the event block
** MAIN Event detected block_count = 0
** MAIN There are 0 blocks for processing
** MAIN Answer block cleared

** PROCESA_BLOQUE STATUS 0
Can't call method "setUnique" on unblessed reference at script/fop2_server.pl line 2235.

Crash ...
I allways see "CallerIDName: <unknown>" when it crashes ...
Edit: no, not always, see next post ...

Thanks for your reply. It is configured by hand. Im running with -X 15 now, logging into a file.

Udo

We have fop2 (Version 2.11) running w/o problems on one server. On a second server, where the configuration is not so much different, fop2 crashes frequently, about 10 times a day or more.

I started fop2 from the command line and got this when it starts (on both servers):

# /usr/local/fop2/fop2_server
Use of uninitialized value in hash element at script/fop2_server.pl line 3991.
Use of uninitialized value in pattern match (m//) at script/fop2_server.pl line 3993.
Use of uninitialized value in integer gt (>) at script/fop2_server.pl line 4001.
Use of uninitialized value in integer gt (>) at script/fop2_server.pl line 4001.
Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 4012.
Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 4012.

When fop crashes, it looks like this:

Use of uninitialized value in string eq at script/fop2_server.pl line 3205.
Can't call method "setUnique" on unblessed reference at script/fop2_server.pl line 2235.

What to do?