search for: notice

...h a Cisco ATA186 and Sipura SPA2000. I have Asterisk, the ATA186 and Sipura all hard coded to G711ulaw. When the fax machine trains, I get a stream of errors in the log file. The log is attached below. If you have any suggestions they would be GREATLY appreciated. Thank you!!! Jan 21 16:06:59 NOTICE[10010661]: Unknown RTP codec 60 received Jan 21 16:06:59 NOTICE[10010661]: Unknown RTP codec 60 received Jan 21 16:06:59 NOTICE[10010661]: Unknown RTP codec 56 received Jan 21 16:06:59 NOTICE[10010661]: Unknown RTP codec 94 received Jan 21 16:06:59 NOTICE[10010661]: Unknown RTP codec 60 received Ja...

...ve posted in the wrong place. I am new to ZFS and this forum. However, this forum appears to be the best place to get good quality ZFS information. Thanks.) Duff ---------------------------------------------------------- Machine 1 Message Log: . . . Sep 13 14:13:22 cypress unix: [ID 836849 kern.notice] Sep 13 14:13:22 cypress ^Mpanic[cpu5]/thread=ffffff000840dc80: Sep 13 14:13:22 cypress genunix: [ID 683410 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=ffffff000840ce90 addr=ffffff01f2b00000 Sep 13 14:13:22 cypress unix: [ID 100000 kern.notice] Sep 13 14:13:22 cypress unix: [ID 839527 kern...

Hi. Just migrated to zfs on opensolaris. I copied data to the server using rsync and got this message: Oct 10 17:24:04 zetta ^Mpanic[cpu1]/thread=ffffff0007f1bc80: Oct 10 17:24:04 zetta genunix: [ID 683410 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=ffffff0007f1b640 addr=fffffffecd873000 Oct 10 17:24:04 zetta unix: [ID 100000 kern.notice] Oct 10 17:24:04 zetta unix: [ID 839527 kern.notice] sched: Oct 10 17:24:04 zetta unix: [ID 753105 kern.notice] #pf Page fault Oct 10 17:24:04 zetta unix: [ID 532287 kern....

...the filesystem? Have I used an alias for the device names that is not valid at boot time? # zpool create -f mtf /dev/dsk/c1t0d0s6 /dev/dsk/c1t1d0s6 /dev/dsk/c1t2d0s6 /dev/dsk/c1t3d0s6 /dev/dsk/c1t4d0s6 /dev/dsk/c1t5d0s6 Dmesg reports the following: Apr 27 09:30:03 weston sata: [ID 663010 kern.notice] /pci at 0,0/pci15d9,8180 at 1f,2 : Apr 27 09:30:03 weston sata: [ID 761595 kern.notice] SATA disk device at port 2 Apr 27 09:30:03 weston sata: [ID 846691 kern.notice] model WDC WD740ADFD-00NL R1 Apr 27 09:30:03 weston sata: [ID 693010 kern.notice] firmware 20.07P20 Apr 27 09:30:03 westo...

Hi all. One of our server had a panic and now can''t mount the zpool anymore! Here is what I get at boot: Mar 21 11:09:17 SERVER142 ^Mpanic[cpu1]/thread=ffffffff90878200: Mar 21 11:09:17 SERVER142 genunix: [ID 603766 kern.notice] assertion failed: ss->ss_start <= start (0x670000b800 <= 0x67 00009000), file: ../../common/fs/zfs/space_map.c, line: 126 Mar 21 11:09:17 SERVER142 unix: [ID 100000 kern.notice] Mar 21 11:09:17 SERVER142 genunix: [ID 802836 kern.notice] fffffe800047e320 fffffffffb9ad0b9 () Mar 21 11:09:17...

...now). A zfs scrub causes a panic under a minute. I can also trigger a panic by doing tars etc. x86 64-bit kernel ... any ideas? Just to help rule out some things, I changed the motherboard, memory and cpu and it still happens ... I also think it happens on a 32-bit kernel. genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=ffffff00100917f0 addr=23b occurred in module "unix" due to a NULL pointer dereference unix: [ID 100000 kern.notice] unix: [ID 839527 kern.notice] sched: unix: [ID 753105 kern.notice] #pf Page fault unix: [ID 532287 kern.notice] Bad kernel fault at a...

...d5ebf3c9" Call-ID: bd57fc656f213326 at 192.168.215.9 CSeq: 16492 ACK User-Agent: Grandstream GXV3000 1.1.3.29 Max-Forwards: 69 Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK Content-Length: 0 <-------------> --- (14 headers 0 lines) --- [Mar 18 11:55:50] NOTICE[13512]: app_meetme.c:1918 conf_run: Audio bytes: 726 Buffer size: 320 [Mar 18 11:55:50] NOTICE[13512]: app_meetme.c:1918 conf_run: Audio bytes: 320 Buffer size: 726 [Mar 18 11:55:50] NOTICE[13512]: app_meetme.c:1918 conf_run: Audio bytes: 930 Buffer size: 320 [Mar 18 11:55:50] NOTICE[13512]:...

...account only. bcoz I can't apply iptables rules on server it's remote server of server provider and we used it for making voip call for customers. for the time been i have close all sip accounts. but can't stop for more then 1 days. I need your help .... *CLI log:- * [Dec 26 21:21:20] NOTICE[1770]: chan_sip.c:22318 handle_request_register: Registration from '"4411" <sip:4411 at 204.152.194.246>' failed for '62.141.54.169' - Wrong password [Dec 26 21:21:20] NOTICE[1770]: chan_sip.c:22318 handle_request_register: Registration from '"4411" &lt...

...o try to fix the problem i changed the timing on span 2 from 0 to 1 span=1,0,0,esf,b8zs bchan=1-23 dchan=24 span=2,1,0,esf,b8zs bchan=25-47 dchan=48 However i still get the same error. Please help we cannot connect call form my norstar to asterisk w/ it dropping in 10 seconds. Jun 12 10:51:51 NOTICE[213005]: PRI got event: 5 on Primary D-channel of span 2 Jun 12 10:51:51 WARNING[213005]: No D-channels available! Using Primary on channel anyway 48!Jun 12 10:51:51 NOTICE[262160]: Alarm cleared on channel 35 Jun 12 10:51:51 NOTICE[262160]: Alarm cleared on channel 36 Jun 12 10:51:51 NOTICE[26216...

...t'': retrying command Jul 8 20:12:59 fortress scsi: [ID 107833 kern.warning] WARNING: / sbus at 1f,0/SUNW,fas at 2,8800000/sd at 6,0 (sd19): Jul 8 20:12:59 fortress Error for Command: write(10) Error Level: Retryable Jul 8 20:12:59 fortress scsi: [ID 107833 kern.notice] Requested Block: 17672154 Error Block: 17672154 Jul 8 20:12:59 fortress scsi: [ID 107833 kern.notice] Vendor: SEAGATE Serial Number: 9946626576 Jul 8 20:12:59 fortress scsi: [ID 107833 kern.notice] Sense Key: Unit Attention Jul 8 20:12:59 for...

...the functionality it provides. What''s not so pleasing is the fact that after installing this, the computer now get very frequent kernel panics. Sometimes it stays up for less than an hour before crashing. The crashes look like this: Nov 12 14:04:15 bahamut unix: [ID 836849 kern.notice] Nov 12 14:04:15 bahamut ^Mpanic[cpu8]/thread=2a101695ca0: Nov 12 14:04:15 bahamut unix: [ID 799565 kern.notice] BAD TRAP: type=34 rp=2a101694c30 addr=60014b2f652 mmu_fsr=0 Nov 12 14:04:15 bahamut unix: [ID 100000 kern.notice] Nov 12 14:04:15 bahamut unix: [ID 839527 kern.notice] sched: Nov 12...

....c:5684 handle_init_event: Detected alarm on channel 29: Yellow Alarm 051008-153001 WARNING[27660]: chan_zap.c:5684 handle_init_event: Detected alarm on channel 30: Yellow Alarm 051008-153001 WARNING[27660]: chan_zap.c:5684 handle_init_event: Detected alarm on channel 31: Yellow Alarm 051008-153001 NOTICE[27660]: chan_zap.c:7428 pri_dchannel: PRI got event: Alarm (4) on Primary D-channel of span 1 051008-153001 WARNING[27660]: chan_zap.c:1938 pri_find_dchan: No D-channels available! Using Primary on channel anyway 16! 051008-153001 NOTICE[27660]: chan_zap.c:5679 handle_init_event: Alarm cleared on...

Hello list, I have nat=no and qualify=no in my sip peer definition and still my CLI is flooded with : [Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (30ms / 2000ms) [Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (24ms / 2000ms) [Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 hand...

...t1xxp Unfortunately it did not help Has anyone run into this in the past? Michael ;zapata.conf switchtype=national context=incoming_eli_pri_1 signalling=pri_cpe group=1 channel => 1-11 bchan=1-11 dchan=24 ;zaptel.conf span=1,1,0,esf,b8zs bchan=1-11 dchan=24 Jun 29 07:09:07 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:07 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:07 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HD...

...aris-dicuss as this probably belongs here.> I kept on trying to migrate my pool with children (see previous threads) and had the (bad) idea to try the -d option on the receive part. The system reboots immediately. Here is the log in /var/adm/messages Feb 8 16:07:09 amber unix: [ID 836849 kern.notice] Feb 8 16:07:09 amber ^Mpanic[cpu1]/thread=ffffff014ba86e40: Feb 8 16:07:09 amber genunix: [ID 169834 kern.notice] avl_find() succeeded inside avl_add() Feb 8 16:07:09 amber unix: [ID 100000 kern.notice] Feb 8 16:07:09 amber genunix: [ID 655072 kern.notice] ffffff00053c4660 genunix:avl_add+59 () Fe...

Say, I just picked this up on my messages! There are a whole host of these requests! Anyone know whow there people are? Is there a way to report them? Any suggestions as to how to block them? [Aug 23 10:34:16] NOTICE[1010] chan_sip.c: Registration from '"912" <sip:1 at 41.1.1.1>' failed for '184.106.217.112' - Wrong password [Aug 23 10:34:16] NOTICE[1010] chan_sip.c: Registration from '"912" <sip:1 at 41.1.1.1>' failed for '184.106.217.112' - Wrong...

I am getting quite a lot of these notices: Feb 1 10:22:01 NOTICE[2487] cdr.c: CDR on channel 'mISDN/3-2' not posted Feb 1 10:22:01 NOTICE[2487] cdr.c: CDR on channel 'mISDN/3-2' lacks end Feb 1 10:22:06 NOTICE[2471] cdr.c: CDR on channel 'mISDN/3-1' not posted Feb 1 10:22:06 NOTICE[2471] cdr.c: CDR on channel...

Howdy, We are using ZFS on one of our Solaris 10 servers, and the box paniced this evening with the following stack trace: Nov 24 04:03:35 foo unix: [ID 100000 kern.notice] Nov 24 04:03:35 foo genunix: [ID 802836 kern.notice] fffffe80004a14d0 fffffffffb9b49f3 () Nov 24 04:03:35 foo genunix: [ID 655072 kern.notice] fffffe80004a1550 zfs:space_map_remove+239 () Nov 24 04:03:35 foo genunix: [ID 655072 kern.notice] fffffe80004a1580 zfs:space_map_claim+32 () Nov 24 04:03:3...

...(sd82): Apr 23 02:02:21 SERVER144 offline or reservation conflict Apr 23 02:02:21 SERVER144 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk at g60001fe100118db00009119074440055 (sd82): Apr 23 02:02:21 SERVER144 i/o to invalid geometry Apr 23 02:02:22 SERVER144 unix: [ID 836849 kern.notice] Apr 23 02:02:22 SERVER144 ^Mpanic[cpu1]/thread=ffffff0017fa1c80: Apr 23 02:02:22 SERVER144 genunix: [ID 809409 kern.notice] ZFS: I/O failure (write on <unknown> off 0: zio ffffffff9a5d4cc0 [L0 bplist] 4000L/4000P DVA[0]=<0:770b24 000:4000> DVA[1]=<0:dfa984000:4000> fletcher4 unco...

...uot;, "(null)", ...): Temporary failure in name resolution [Mar 21 09:57:04] WARNING[6748] acl.c: Unable to lookup 'pbx2.server.com' ----------------------------------------------------------------THEN ------------------------------------------------------------- [Mar 21 09:57:04] NOTICE[6748] chan_sip.c: Peer 'YYYY' is now UNREACHABLE! Last qualify: 10 [Mar 21 09:57:04] NOTICE[6748] chan_sip.c: Peer 'C1045' is now UNREACHABLE! Last qualify: 140 [Mar 21 09:57:04] NOTICE[6748] chan_sip.c: Peer 'XXXX' is now UNREACHABLE! Last qualify: 33 [Mar 21 09:57:15] N...