search for: restarting

Hello, As you can see are pri is being reset every 60 minutes! Is there a way to stop this?? Is it a Zapata configuration problem? We have a * box with a single port T1/pri card installed. Thanks lach Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 2 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 3 successfully restarted on span 1 Apr 7 09:00:07

Hi All, Hope you all are fine and good, Today i have found that Mine all PRI Channels are restating after every interval of one hour, and i have search and psot on fourms and everyone said that this is a normal behaviour. If this is a normal behaviour is there is any way to stop it { i still don't know what is the reson to restart ever hour } . Because this is listed everywhere that

My TE110P reset some times in the day. E this cause an interruption in the service. How I decide this problem? my zaptel.conf span=1,1,0,esf,b8zs bchan=1-23 # set this to 1-15,17-31 for E1 dchan=24 # set this to 16 for E1 defaultzone=us loadzone=us my zapata.conf [channels] language=en signalling=pri_cpe switchtype=national echocancel=yes echocancelwhenbridged=yes echotraining=200 ; Asterisk

Hi! I have an Asterisk Box with one E1. This is connected with PSTN. My problem is that periodically the Asterisk console shows the following message. -- B-channel 0/1 succesfully restarted on span 1 -- B-channel 0/2 succesfully restarted on span 1 -- B-channel 0/3 succesfully restarted on span 1 -- B-channel 0/4 succesfully restarted on span 1 -- B-channel 0/5 succesfully restarted on span 1 --

Hey, I'm up and running fine with 30 Polycom 500s connected to Asterisk 1.2Beta on Cent OS 4.1 with a Digium TE110 connected to a PRI line. Nearly every hour, almost on the hour I get this: Sep 29 23:01:38 VERBOSE[3567] logger.c: -- B-channel 0/1 successfully restarted on span 1 Sep 29 23:01:38 VERBOSE[3567] logger.c: -- B-channel 0/2 successfully restarted on span 1 Sep 29

I have just finished installing a new asterisk box at my work. The box is quite hefty, dual Zeon 2.8s with SCSI drives and 2Gb of memory. I have a 4 port Digium T1 card for channel bank and PRI access. I activated a PRI from a local CLEC (DMS-500 based, National protocol). This PRI is on slot 2 of the card and is set as the primary timing source. It is ESF/B8ZS. All the software is latest

...uot;owns" those domUs let windows updates install and then restart, which they failed to restart. When I tried to manually restart them I was getting can''t allocate memory errors. In the past I''ve had can''t allocate memory errors when trying to bring up a new domU. Restarting virt-manager usually clears that. This time it did not help. So I restarted xend. Only problem is it restarting all the domUs that were running ok. 1) Is that the expected behavior? (restarting xend restarts all domUs) 2) Is there anything else I should have checked or done for the memory erro...

Hi, I'm getting the following error from an asterisk 1.6.0.9 installation: [May 20 06:07:18] ERROR[18517]: chan_dahdi.c:10515 dahdi_pri_error: Asked to delete sched id -1??? [May 20 06:07:18] ERROR[18517]: chan_dahdi.c:10515 dahdi_pri_error: No more room in scheduler This repeats a few times, then asterisk crashes. I can't seem to locate any info on this error at all. I'm using

Hi , I'm having a problem that really bothers me , I have looked for similar cases but couldn't really find an answer . I keep getting messages which says that -- B-channel xx successfully restarted on span x and this causes the calls to be disconnected if somone is already using the channel that is being restarted, plz notice below the under lined text in which I was testing and

I'm running * 1.4 and can successfully restart asterisk from the command line with: /usr/sbin/asterisk -r -x "restart gracefully" However, I have a cron job that tries to restart asterisk and gets this error: No such command 'restart gracefully' (type 'help restart gracefully' for other possible commands) Can anyone think of why this is happening? Thanks

I''ve got switchtower set up, and it seems to work fine except for one problem: It doesn''t successfully restart lighttpd. I have the following task in my deploy.rb file: desc "Restart the web server" task :restart, :roles => :app do sudo "/usr/local/etc/rc.d/lighttpd.sh restart" end This is on a FreeBSD system, so it''s using the rc script to

Greetings. Today I've installed a fresh new E100P on a EuroISDN PRI. It seems to work well, accepting calls, but, when I start *, I have the screen flooded with this message: PRI got event: 8 (or 6) If i look into /var/log/asterisk/messages i've this Error: File chan_zap.c, Line 5341 (zt_pri_error): PRI: Read on 35 failed: Unknown error 500 Repeated indefinitely. Also, i've a

...ice: /Stage[main]/Ast_win::Restart/Exec[restart_agent]/returns: Notice: /Stage[main]/Ast_win::Restart/Exec[restart_agent]/returns: ************* ************************************************************* Notice: /Stage[main]/Ast_win::Restart/Exec[restart_agent]/returns: Install Stage Complete. Restarting the puppet service. Notice: /Stage[main]/Ast_win::Restart/Exec[restart_agent]/returns: IF USING A COMMAND PROMPT, YOU MUST NOW CLOSE IT AND OPEN A NEW ONE BEFORE CONTINUING! Notice: /Stage[main]/Ast_win::Restart/Exec[restart_agent]/returns: ************* *****************************************...

I want to restart my Mongrels from crontab periodically to free up memory. I tried this: [admin at mudcrapce ~]$ mongrel_rails cluster::restart -C /var/www/apps/mudcrapce/current/config/mongrel_cluster.yml Restarting 5 Mongrel servers... mongrel_rails restart -P log/mongrel.3040.pid !!! PID file log/mongrel.3040.pid does not exist. Not running? mongrel::restart reported an error. Use mongrel_rails mongrel::restart -h to get help. Mongrel''s cluster restart has these options: [admin at mudcrapce ~]$ mon...

Is it normal for the following to occur hourly on an E1 PRI ? -- B-channel 0/1 successfully restarted on span 1 -- B-channel 0/2 successfully restarted on span 1 -- B-channel 0/3 successfully restarted on span 1 -- B-channel 0/4 successfully restarted on span 1 -- B-channel 0/5 successfully restarted on span 1 -- B-channel 0/6 successfully restarted on span 1 --

Has anyone else had this symptom? It seems like my PRI ?restarts? each hour. I?ve got a PRI from Qwest in central California. What I don?t know is if this is on the * side or on the telco side. I don?t use my system enough to know if this is a big problem, a minor glitch or just an ?undocumented feature? - ? Any suggestions on how to track the source of these ?restarts?? Anybody else seen

I just created a new rails project "test". I then did "switchtower --apply-to ~/user/test test" I then moved into test and tried "rake restart" and got: kfelkins@lurch:~/user/test$ rake restart (in /home/kfelkins/user/test) rake aborted! Don''t know how to build task ''restart'' I see restart in deploy. Can restart be invoked from the

...l on span 1 up B-channel 2 successfully restarted on span 1 B-channel 3 successfully restarted on span 1 B-channel 4 successfully restarted on span 1 B-channel 5 successfully restarted on span 1 .... And so forth with the D-channel going up and down and various channels "successfully restarting" but inbound calls do not work. I have tried changing the PRI protocol, I have swapped the CPE and NET settings between the PBX and Asterisk and every combination gives me this same result. Any thoughts? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... U...

Hi, I am using xen-4.1-testing with Linux 3.4.3. The hotplug script xencommons echoes that xenstore is not restartable. Can anyone tell me the exact reason why it is not restartable. I tried to restart xenstore by killing the xenstore and restarting it with xencommons but after that VM creation doesn''t work. I used to do the same with the setting <xen-3.4+Linux-2.6.18> and it used to work fine. thanks, Shakeel

Hi all, Forgive me if this has been asked before, but is there a reason mongrel_rails cluster::restart stops all ports and then restarts them again? Wouldn''t it be better to restart each port one-by-one in series so that upstream proxy servers can fail over while the restart is occurring, or am I missing something? Thanks, eden