> that merge-logs was not producing useful output, which seems to have been
> due to user error (in particular, not getting logging set to INFO level).
> So there's no reason to carry on worrying about the situation.
It was actually because I was looking for the wrong number but still user error
Finally found it.
I've been looking for ntpd all along because I had removed my ntpdate script
which was using ntpdate.
I had a second script sitting in /etc/cron.hourly and never looked there. Since
I wasn't looking for ntpdate, nothing ever came up.
I was using grep for example, searching sp
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
[m...@grounded.net]
The only ntpd mention is the running process which never changes pid.
grep "ntpd" really-big-file
6374 ?SLs
> (One thing to check: is ntpd.conf's modification date reasonable?
Looks right. That's about the time I last changed anything on it.
# ls -la /etc/ntp.conf
-rw-r--r-- 1 root root 784 Jul 13 17:36 /etc/ntp.conf
# more /etc/ntp.conf
tinker panic 0
restrict default kod nomodify notrap nopeer noque
sipx-users] Random Dropped Registrations
Any of a million things could be happening.
(One thing to check: is ntpd.conf's modification date reasonable? If its
date got mis-set *into the future*, some process might be trying to restart
NTP over and over, because it always thinks ntp.conf was just
Any of a million things could be happening.
(One thing to check: is ntpd.conf's modification date reasonable? If its date
got mis-set *into the future*, some process might be trying to restart NTP over
and over, because it always thinks ntp.conf was just changed.)
But to find out "what is rest
starting?
> -Original Message-
> From: sipx-users-boun...@list.sipfoundry.org
> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of
> m...@grounded.net
> Sent: Friday, July 16, 2010 9:28 AM
> To: sipx-users
> Subject: Re: [sipx-users] Random Dropped Registrations
>
> E
Early in this thread, I was reminded that I should not run ntpdate when ntpd is
running. I had a cron job running every hour, which would stop ntpd, run
ntpdate, then restart ntpd. That of course was removed. Now, as it should, ntpd
is started when the system boots and should maintain the clock,
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
[m...@grounded.net]
I don't know if you would like me to still use the old system to learn about
getting the output etc, or keep your not
> That's fine, but I instructed you to *note down the extension of an
> affected phone*, and you did not do that. The importance of that step may
> not be obvious, but I've learned the hard way that when trying to fix a
I fully agree, and I need to be more detailed when I have problems with sipx.
I'll get back on this soon. Got back from the weekend only to find that we
suffered a power failure and of course, one of the secondary UPS's decided it
was time to have a battery problem and didn't keep the load up long enough for
the geny to kick in. I have this mess to deal with and resolve.
I re-ran the test using a device which is registered.
# merge-logs --ft=xxx3100 --include-method=register
# ls -la merged.xml
-rw-r--r-- 1 root root 54916 Jul 9 15:58 merged.xml
I have content in the merged.xml file now.
I see why it didn't work when I quickly tried it before at least. We hav
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
[m...@grounded.net]
# merge-logs --ft=xx1760 --include-method=register
# ls -la merged.xml
-rw-r--r-- 1 root root 79 Jul 9 14:14 me
> That is, the
> components are logging at WARNING level, not INFO level. You'll have to
> fix that, which is step 1 in the diagnostic process I sent you.
I usually leave it to info unless there is a need to set it otherwise. I'll set
them, then save them and see if that helps.
Maybe something g
In regard to the merge-logs problem, examining the log files, it turns out that
they do not contain the incoming/outgoing messages. That is, the components
are logging at WARNING level, not INFO level. You'll have to fix that, which
is step 1 in the diagnostic process I sent you. After that,
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
[m...@grounded.net]
>?If you have observed a phone disappearing from the Active
>?Registrations screen (as instructed in step (2)), you'd
To Scott;
> It's entirely possible that you just didn't notice, or that the changes
> to your clock started happening recently (that would be my bet).
It's a very obvious problem, just started happening maybe a month ago but got
worse recently.
To Tony;
>Your hardware issue is unique. None of
On 2010-07-08 11:18, m...@grounded.net wrote:
> And a big fat 'Ah, so something DID change in sipx that made this pronounced
> all of a sudden!'.
>
No. A clock behaving the way yours did would mess up any version of
sipXecs that was ever built (or ever will be - time must be a one-way
system)
Message -
From: sipx-users-boun...@list.sipfoundry.org
To: sipx-users
Sent: Thu Jul 08 11:18:32 2010
Subject: Re: [sipx-users] Random Dropped Registrations
On Thu, 8 Jul 2010 11:10:58 -0400, Tony Graziano wrote:
> Big fat I told you so.
And a big fat 'Ah, so something DID change in s
On Thu, 8 Jul 2010 11:10:58 -0400, Tony Graziano wrote:
> Big fat I told you so.
And a big fat 'Ah, so something DID change in sipx that made this pronounced
all of a sudden!'.
> In 4.2 some processes use a bit more cpu power, and that's likely why it
> pronounced itself.
I'm hoping I can find
users] Random Dropped Registrations
Have yet to receive answers from IBM but the problem went away on an HP
stand alone server.
Wish I understood why the problem just recently showed up because I've been
using these blades for about a year and a half and never saw the problem.
At least now I kno
Have yet to receive answers from IBM but the problem went away on an HP stand
alone server.
Wish I understood why the problem just recently showed up because I've been
using these blades for about a year and a half and never saw the problem.
At least now I know about it so can work on that an
> If you have observed a phone disappearing from the Active
> Registrations screen (as instructed in step (2)), you'd know which
> phone was involved:
There were about a dozen phones registered in the list and when the problem
happened, it would take them all out.
> If you are having registratio
> From: sipx-users-boun...@list.sipfoundry.org
> [sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
> [m...@grounded.net]
>
> >>?6) Do "merge-logs --ft=[extension] --include-method=register", where
> >>?[extension] is the extension of the phone in question. ?This extracts
>
I'm going to install another server so I can see if this happens on a stand
alone.
In getting things ready, I noticed that I was still using the 32Bit ISO while
the blades are 64Bit.
I did so because people have said this should not be an issue but is it
possible that it is related?
I'm asking
> There is no doubt whatsoever that your clock is being changed by
> something, and that is the root of your major problem. Quit wasting
> time wondering if it is strange and find what's messing up your clock.
Scott, I'm not trying to waste any time, I'm trying to make sure I have input
for the
On Wed, 07 Jul 2010 13:24:05 -0500, Matthew Kitchin (public/usenet) wrote:
> The system time is going backwards and forwards. That is a fact. See
> below. Sipx is not changing your time. You need to figure out what is
> changing your time. That will solve many or all of your problems.
Yes, you're
On 2010-07-07 14:19, m...@grounded.net wrote:
>> Yes.
> Ok, wanted to make sure I didn't miss something.
>
>> I made note that the last time the problem happened was around 11:01.
>> Notice that I started your test script to at 10:23, and it ended at 11:47.
>> The output from that test sh
Is there a setting similar to:
http://www-03.ibm.com/systems/i/advantages/integratedserver/faqinstall.html#timesyc
This message and any files transmitted with it are intended only for the
individual(s) or entity named. If you are not the intended individual(s) or
entity named you are hereby n
The system time is going backwards and forwards. That is a fact. See
below. Sipx is not changing your time. You need to figure out what is
changing your time. That will solve many or all of your problems.
Wed Jul 7 11:00:55 CDT 2010
Wed Jul 7 11:00:56 CDT 2010
Wed Jul 7 11:00:57 CDT 2010
Wed
> Yes.
Ok, wanted to make sure I didn't miss something.
> I made note that the last time the problem happened was around 11:01.
> Notice that I started your test script to at 10:23, and it ended at 11:47.
> The output from that test shows that system time never went backwards.
> However, the sip
Yes.
-Original Message-
From: "m...@grounded.net"
Sender: sipx-users-boun...@list.sipfoundry.org
Date: Wed, 7 Jul 2010 13:01:40
To: sipx-users
Reply-To: m...@grounded.net
Subject: Re: [sipx-users] Random Dropped Registrations
>See my next email. It is going backwards
29:03 CDT 2010 I have also attached
>>> the output from the basic time check script which I ran. >
>>> ============ Tony Graziano, Manager Telephone:
>>> 434.984.8430 Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net
>>> LAN/Tele
asic time check script which I ran.>
>>> Tony Graziano, Manager Telephone:
>>> 434.984.8430 Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net
>>> LAN/Telephony/Security and Control Systems Helpdesk: Telephone:
&g
Telephone:
>> 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers:
>> http://www.myitdepartment.net/gethelp/ - Original Message -
>> From: sipx-users-boun...@list.sipfoundry.org
>>> To: sipx-users >> us...@list.sipfoundry.org> Sent:
Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427
Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/
- Original Message -
From: sipx-users-boun...@list.sipfoundry.org
To: m...@grounded.net
Cc: sipx-users
Sent: Wed Jul 07 13:41:05 2010
Subject: Re: [sipx-users] Random Dropped Regi
epartment.net
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427
Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/
- Original Message -
From:sipx-users-boun...@list.sipfoundry.org
To: sipx-use
434.984.8426
Fax: 434.984.8427
Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/
- Original Message -
From: sipx-users-boun...@list.sipfoundry.org
To: sipx-users
Sent: Wed Jul 07 12:32:02 2010
Subject: Re: [sipx-users] Random Dropp
On 2010-07-07 13:30, m...@grounded.net wrote:
> What is interesting is that it happened around 11:01 or so and looking at the
> sipregistry.log file, the times are totally weird as was identified yesterday.
>
> I have ntpd turned off at the moment.
> Looking at the above file, we see when we rol
rol Systems Helpdesk:
> Telephone: 434.984.8426
> Fax: 434.984.8427
>
> Helpdesk Contract Customers:
> http://www.myitdepartment.net/gethelp/
>
> - Original Message -
> From: sipx-users-boun...@list.sipfoundry.org
>
> To: sipx-users
> Sent: Wed Jul 07 12:32:
On 2010-07-07 12:55, m...@grounded.net wrote:
>>> for i in {1..5000}
>>> do
>>> date>>/tmp/timecheck
>>> sleep 1
>>> done
> This completed but of course, it's a large file and hard to know if any
> timing was missed.
> Anyone know of a command or little to check this output file now?
>
On 2010-07-07 12:27, m...@grounded.net wrote:
>>> 1) Set your logging level to INFO (or DEBUG if you like that better).
> It is set to info or, all default at this time.
>
>>> 2) Wait for the problem to be manifest, that is, a phone is first seen
>>> and then later not seen on the Active Re
Zip the timecheck file and send it on. It should compress significantly.
On 7/7/2010 11:55 AM, m...@grounded.net wrote:
for i in {1..5000}
do
date>>/tmp/timecheck
sleep 1
done
This completed but of course, it's a large file and hard to know if any timing
was missed.
Anyone kn
>> for i in {1..5000}
>> do
>> date>>/tmp/timecheck
>> sleep 1
>> done
This completed but of course, it's a large file and hard to know if any timing
was missed.
Anyone know of a command or little to check this output file now?
The output looks like;
Wed Jul 7 10:23:37 CDT 2010
Wed Jul 7 10:2
:
Telephone: 434.984.8426
Fax: 434.984.8427
Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/
- Original Message -
From: sipx-users-boun...@list.sipfoundry.org
To: sipx-users
Sent: Wed Jul 07 12:32:02 2010
Subject: Re: [sipx-users] Random Dropped Registrations
I am
I am following everyone's suggestions. I am providing what ever output is
required of me.
Would be happy to send my snapshot to someone who may be able to check it as
the merge-logs problem is one of the original issues.
___
sipx-users mailing list
>> 1) Set your logging level to INFO (or DEBUG if you like that better).
It is set to info or, all default at this time.
>> 2) Wait for the problem to be manifest, that is, a phone is first seen
>> and then later not seen on the Active Registrations screen without any
>> explanation.
As suggest
> But those lines were not in what you sent before.
My last post from this morning at 2am contained the error lines mentioned. It's
become a crazy long thread so hard to keep up.
If this is not what you're talking about, sorry, I'm working on lack of sleep
and a great deal of stress so easy to m
On Wed, 7 Jul 2010 10:28:42 -0400, Tony Graziano wrote:
> How about fixing the timing on your blade center? I think lots of people
> will be happy to have that working properly!
>
> Once that is fixed let's wait to hear if you have anymore "lost"
> registrations.
Fair enough, I've asked in the I
> Since your clock gets messed up once per hour, and you've previously stated
> that you had a cron job that ran every hour that set the time, that cron
> job is the most obvious suspect.
I no longer have the additional ntpdate command running, nor anything else
doing time controls.
Other than si
> From: sipx-users-boun...@list.sipfoundry.org
> [sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
> [m...@grounded.net]
>
> Here it is, the complete run. I deleted the old merged.xml file just to be
> 100% sure.
>
> # merge-logs
>
> # ls -la merged.xml
> -rw-r--r-- 1 ro
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
[m...@grounded.net]
>?From Dale's observation, you have another cron job somewhere that's
>?resetting the clock every hour.
Fair enough b
d Jul 07 11:08:07 2010
Subject: Re: [sipx-users] Random Dropped Registrations
On Wed, 7 Jul 2010 05:32:26 -0400, Tony Graziano wrote:
> Do us all a favor and consider changing your terminology here.
Sure, so what should I call it then? I've called it dropped, but always said
from the list
On Wed, 7 Jul 2010 05:32:26 -0400, Tony Graziano wrote:
> Do us all a favor and consider changing your terminology here.
Sure, so what should I call it then? I've called it dropped, but always said
from the list in the Active Registration screen.
> as in I was registered and the registrar seeme
users@list.sipfoundry.org
> Sent: Wed Jul 07 10:51:35 2010
> Subject: Re: [sipx-users] Random Dropped Registrations
>
> Maybe running a script like this will shed some light on your time issues.
>
> for i in {1..5000}
> do
> date>>/tmp/timecheck
> sleep 1
> d
users-boun...@list.sipfoundry.org
To: sipx-users@list.sipfoundry.org
Sent: Wed Jul 07 10:51:35 2010
Subject: Re: [sipx-users] Random Dropped Registrations
Maybe running a script like this will shed some light on your time issues.
for i in {1..5000}
do
date >>/tmp/timecheck
sleep 1
done
This s
Maybe running a script like this will shed some light on your time issues.
for i in {1..5000}
do
date >>/tmp/timecheck
sleep 1
done
This should output the time every second to a file for 5000 seconds. It
may give you an idea of when your clock is going haywire.
On 7/7/2010 9:28 AM, Tony
On 2010-07-07 10:23, m...@grounded.net wrote:
> Just prior to the problem being repeated, everything looked normal, we saw no
> errors anywhere. This is why I didn't post the entire log and only a few
> seconds prior. When we were able to duplicate the problem, we were watching
> wireshark, ru
How about fixing the timing on your blade center? I think lots of people
will be happy to have that working properly!
Once that is fixed let's wait to hear if you have anymore "lost"
registrations.
On Wed, Jul 7, 2010 at 10:23 AM, m...@grounded.net wrote:
> > You provided approximately 33 second
> You provided approximately 33 seconds of log data, and did not tell us
> the time window during which the registrations disappeared.
Didn't think you would want it because the relevant part seems to be when the
problem occurs. It appears to be a timer related issue.
I found some mentions of wha
On 2010-07-07 0:26, m...@grounded.net wrote:
> It happened again about 5 minutes ago. I grabbed a snippet after all of the
> registered phones had dropped. At the time I took this, there were no phones
> registered.
You provided approximately 33 seconds of log data, and did not tell us
the ti
Just to clarify a bit, Tony, I think you mean that the below command is
relevant in this case:
>And of course, I set the hardware clock using the system time;
>hwclock --systohc
It could be that on Mike's system the hardware clock is set every hour or
so by the "hwclock" command, basically push
Do us all a favor and consider changing your terminology here.
"dropped" and is in the middle of a call and dropped the call, and "lost"
(or lose) registration as in I was registered and the registrar seemed to
determine that my registration was no longer active.
ensure your cron jobs have nothin
Sorry if this gets posted twice, it didn't seem to make it so I put the file on
a web server instead of attaching.
> What's under devices/network parameters for NTP?
1.pool.ntp.org Enabled 1.pool.ntp.org NTP
2.pool.ntp.org Enabled 2.pool.ntp.org NTP
Finally found a lead. We had been waiting to
> by far the most frequent poster), and almost all of yours are completely
> lacking anything like sufficient information or clarity that anyone can
I provide what information I can based on the input I get. I provide everything
I'm asked for and don't hold back. As you know, I also have some pro
On Tue, 06 Jul 2010 22:51:14 -0500, Josh Patten wrote:
> Does merge-logs need to be run within the /var/log/sipxpbx directory? I
> seem to recall that being necessary.
From what I understand, it does, and I do.
___
sipx-users mailing list sipx-users@li
Does merge-logs need to be run within the /var/log/sipxpbx directory? I
seem to recall that being necessary.
On 07/06/2010 10:09 PM, m...@grounded.net wrote:
Fix your clock - make sure that all timestamps in the logs are moving
forward.
This is the task at hand for sure.
your
> Fix your clock - make sure that all timestamps in the logs are moving
> forward.
This is the task at hand for sure.
> your ntp server sync stays stable over at least several hours.
So far, both hardware and OS are perfectly on time.
> Until you do this, _NOTHING_ else is worth spending time o
> No - all sipXecs logs are deliberately recorded only in UTC. That
> allows us to correlate events that occur in servers regardless of what
> timezone the servers are in.
Ok, so then it's normal for the logs to have that time. Guess I never noticed
that before. Never searched by time I guess, o
> You are using NTP incorrectly and it is messing up your clock, which is
> then messing up registrations. Actually, all kinds of things will be
> fowled up by this - it's amazing you have not had other problems.
Ok, I have no issues with being wrong about something but there's only one way
to l
On 2010-07-06 22:17, m...@grounded.net wrote:
> I've not cleared my logs in a day or two now and decided to double check that
> merge-logs in indeed installed, as I'm sure I ran it.
> This time, it took a rather long time to run so figured perhaps it didn't
> have enough logs when I've run it b
> I don't see the command line that executed merge-logs. Did it report a
> "not found" error as you say it has done in the past? Show us what
> happened!
What is there to show??? It doesn't output anything, it just creates the
merged.xml file.
As I said, I want to start a different thread for
On 2010-07-06 22:35, m...@grounded.net wrote:
> I've never seen this on any other server I've got so this is beyond my
> knowledge.
> I'm central US time, I have an offset of -360 set in the GMT Offset in sipx.
> This is what I have set in ntp.conf.
>
> So, I have a UTC setting somewhere which i
On 2010-07-06 22:36, m...@grounded.net wrote:
> So I have a UTC and GMT conflict somewhere?
No - timezones have nothing to do with it.
You are using NTP incorrectly and it is messing up your clock, which is
then messing up registrations. Actually, all kinds of things will be
fowled up by this
Are you losing your mind or something and just picking me to blame?
> I have just asked you to run certain commands and report the output. You
> have not, in fact, then run the commands and reported the output, you have
> simply said that you have previously done so in some place that you don't
>
Wow Dale, that's is one very weird reply. Why even help if all it does it piss
you off?
Man that's just too weird.
> I have no idea. But I have no interest in solving your NTP problems.
> Presumably you are responsible for doing so. When you get the time problem
> fixed, see if you still get
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
[m...@grounded.net]
I've not cleared my logs in a day or two now and decided to double check that
merge-logs in indeed installed, as I'm
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
[m...@grounded.net]
So I have a UTC and GMT conflict somewhere?
I have no idea. But I have no i
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
[m...@grounded.net]
>?In this instance you've said "The merge-logs command and the regtimes
>?command don't [exist] on the ISO", but you h
ndry.org
> Date: Tue, 6 Jul 2010 21:29:02
> To: sipx-users
> Reply-To: m...@grounded.net
> Subject: Re: [sipx-users] Random Dropped Registrations
>
> We've not seen a pattern yet but I'm watching to see if that is related.
> For example, maybe as someone mentioned
So I have a UTC and GMT conflict somewhere?
On Tue, 6 Jul 2010 22:28:33 -0400, WORLEY, Dale R (Dale) wrote:
>
>
> From: sipx-users-boun...@list.sipfoundry.org [sipx-users-
> boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
> [m...@grounded.net]
I've never seen this on any other server I've got so this is beyond my
knowledge.
I'm central US time, I have an offset of -360 set in the GMT Offset in sipx.
This is what I have set in ntp.conf.
So, I have a UTC setting somewhere which is overriding?
On Tue, 06 Jul 2010 22:30:38 -0400, keccle
der: sipx-users-boun...@list.sipfoundry.org
Date: Tue, 6 Jul 2010 21:29:02
To: sipx-users
Reply-To: m...@grounded.net
Subject: Re: [sipx-users] Random Dropped Registrations
We've not seen a pattern yet but I'm watching to see if that is related. For
example, maybe as someone mentioned before, one of the p
On Tue, 2010-07-06 at 21:25 -0500, m...@grounded.net wrote:
> I'm sort of back to something I noticed a while back in this thread, when I
> mentioned that the server has the right time but the live logs don't. I'm
> watching the sipregistrar.log going by, the system has the proper time but
> the
> Reply-To: m...@grounded.net
> Subject: Re: [sipx-users] Random Dropped Registrations
>
> Same as explained before, dropped, vanished, from the list of Active
> Registrations.
> Slowly but surely, they have all come back and I'm watching to see when it
> happens again.
> I&
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
[m...@grounded.net]
>?Get the sipregistrar.log from one of your failure windows and post it
>?somewhere to which you can provide a URL, th
sipx-users
Reply-To: m...@grounded.net
Subject: Re: [sipx-users] Random Dropped Registrations
Same as explained before, dropped, vanished, from the list of Active
Registrations.
Slowly but surely, they have all come back and I'm watching to see when it
happens again.
I'm
I'm sort of back to something I noticed a while back in this thread, when I
mentioned that the server has the right time but the live logs don't. I'm
watching the sipregistrar.log going by, the system has the proper time but the
logs don't!
# date
Tue Jul 6 21:24:59 CDT 2010
Then tail the log
sipx-users
> Reply-To: m...@grounded.net
> Subject: Re: [sipx-users] Random Dropped Registrations
>
> The problem is not solved. The time is correct and all phones just dropped
> again.
> Happy to send a snapshot privately.
>
>> In this instance you've said "The mer
I've not cleared my logs in a day or two now and decided to double check that
merge-logs in indeed installed, as I'm sure I ran it.
This time, it took a rather long time to run so figured perhaps it didn't have
enough logs when I've run it before.
Thing is, even though it definitely took longer t
What does dropped mean in this specific case?
-Original Message-
From: "m...@grounded.net"
Sender: sipx-users-boun...@list.sipfoundry.org
Date: Tue, 6 Jul 2010 21:12:43
To: sipx-users
Reply-To: m...@grounded.net
Subject: Re: [sipx-users] Random Dropped Registrations
The prob
The problem is not solved. The time is correct and all phones just dropped
again.
Happy to send a snapshot privately.
> In this instance you've said "The merge-logs command and the regtimes
> command don't [exist] on the ISO", but you haven't *copied down the details
> of the failure*. What is t
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of dan [...@dm3.us]
The logs are in UTC aren't they? Central Daylight time is 5 hours behind UTC.
___
Yes, the log
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
[m...@grounded.net]
One thing I forgot to note is that someone was on the phone when all of the
registered devices went away but she neve
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
[m...@grounded.net]
>?6) Do "merge-logs --ft=[extension] --include-method=register", where
>?[extension] is the extension of the phone in
>Use the ntp.conf configuration created for you by the setup script -
>someone send him a copy
Copy of what? The ntp servers are in the ntp file.
> network - your firewall may need to be configured). A quick google
> search will tell you how to check whether or not it is working (and/or
> others
My bad. I'm on a bberry wand was doing it from memory.
-Original Message-
From: "m...@grounded.net"
Sender: sipx-users-boun...@list.sipfoundry.org
Date: Tue, 6 Jul 2010 20:12:10
To: sipx-users
Reply-To: m...@grounded.net
Subject: Re: [sipx-users] Random Dropped Registrat
On 2010-07-06 21:40, m...@grounded.net wrote:
> On Tue, 6 Jul 2010 23:47:48 +, Matthew Kitchin (Public) wrote:
>> Can you paste output from crontab -l and the file /etc/ntpd.conf
> Sure, nothing in crontab;
>
> # crontab -l
> no crontab for root
>
> And there is no ntpd.conf in /etc/
>
> I
On Tue, 6 Jul 2010 23:47:48 +, Matthew Kitchin (Public) wrote:
> Can you paste output from crontab -l and the file /etc/ntpd.conf
Sorry, it's ntp.conf;
# more ntp.conf
# ntpd configuration
# --
#
# Permit time synchronization with our time source, but do not
# permit the sourc
On Wed, 7 Jul 2010 00:49:57 +, Matthew Kitchin (Public) wrote:
> I would set the clock to the correct time and disable any and all time
> synch mechanisms for your server for now. That is just my opinion. I don't
> think any amount of clock drift could be worse than the problems you are
> havin
1 - 100 of 140 matches
Mail list logo
