I just fetched today's cvs (1/30/04 11:10:31). Compiles/installs on my test machine (ASUS A7V, 900 MHZ). However, If I try to compile on my production machine (Elite K7S5A, 2.4GHz, 512MB) while * is running the zaptel and asterisk compiles seg fault. I am assuming that they will compile correctly if I bring down * and rmmod the zaptel driver. 0.7.1 compiled and is now running. Is there a way to safely compile while * is running, so that I can minimize down time of the server?
On Fri, Jan 30, 2004 at 12:21:49PM -0500, Stephen R. Besch wrote:> I just fetched today's cvs (1/30/04 11:10:31). Compiles/installs on my > test machine (ASUS A7V, 900 MHZ). However, If I try to compile on my > production machine (Elite K7S5A, 2.4GHz, 512MB) while * is running the > zaptel and asterisk compiles seg fault. I am assuming that they will > compile correctly if I bring down * and rmmod the zaptel driver. 0.7.1 > compiled and is now running. > > Is there a way to safely compile while * is running, so that I can > minimize down time of the server?Seg faulting compiles usually indicate a memory problem on the machine. Not lack of size, but bad memory, badly seated memory, etc... There's no reason asterisk running, or the drivers being loaded, should cause a compile to seg fault. On the other hand, the load of a compile could affect asterisk's performance... Rob -- Rob Fugina, Systems Guy robf@geekthing.com -- http://www.geekthing.com My firewall filters MS Office attachments. Yes, you're right. Unfortunately, I don't really care.
While your problem is most likely bad RAM as other replies have suggested, there is another thing to keep in mind. Some implementations of dynamic module loading have problems if a loaded module is overwritten on the disk. What this means is that it is safest to stop Asterisk just before running "make install", else the running instance may mysteriously segfault at that point. /w -- /~\ The ASCII Ribbon Campaign \ / No HTML/RTF in email X No Word docs in email / \ Respect for open standards
Nope I do make install all the time with asterisk running without ONE problem. bkw On Sat, 31 Jan 2004, William Waites wrote:> While your problem is most likely bad RAM as other > replies have suggested, there is another thing to > keep in mind. > > Some implementations of dynamic module loading have > problems if a loaded module is overwritten on the > disk. What this means is that it is safest to stop > Asterisk just before running "make install", else > the running instance may mysteriously segfault at > that point. > > /w > -- > /~\ The ASCII Ribbon Campaign > \ / No HTML/RTF in email > X No Word docs in email > / \ Respect for open standards > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
On Sat, Jan 31, 2004 at 07:43:46PM -0600, Brian West wrote:> Nope I do make install all the time with asterisk running without ONE > problem.As I said, this behaviour is specific to some implementations of dynamic loadable modules. It depends what OS (and in some cases what version of the OS) you are running. /w -- /~\ The ASCII Ribbon Campaign \ / No HTML/RTF in email X No Word docs in email / \ Respect for open standards
On Sat, 2004-01-31 at 20:02, William Waites wrote:> On Sat, Jan 31, 2004 at 07:43:46PM -0600, Brian West wrote: > > Nope I do make install all the time with asterisk running without ONE > > problem. > > As I said, this behaviour is specific to some implementations > of dynamic loadable modules. It depends what OS (and in some > cases what version of the OS) you are running.Dude maybe you need to learn more Unix programing and leave those toy OSes alone. Once a module is loaded, there should be no need to read the version on the file system again. Your problem would be loading new modules into a running version where there may have been an api change. -- Steven Critchfield <critch@basesys.com>
Stephen R. Besch wrote:> I just fetched today's cvs (1/30/04 11:10:31). Compiles/installs on my > test machine (ASUS A7V, 900 MHZ). However, If I try to compile on my > production machine (Elite K7S5A, 2.4GHz, 512MB) while * is running the > zaptel and asterisk compiles seg fault. I am assuming that they will > compile correctly if I bring down * and rmmod the zaptel driver. 0.7.1 > compiled and is now running. > > Is there a way to safely compile while * is running, so that I can > minimize down time of the server? >Here's the update on the seg fault problems. After "bad" memory was suggested, I checked to see what memory the tech who assembled the machine had used. I don't know why, but the module was not in the recommended list for the MOBO at Crucial.com. I ordered one of the recommended modules. It arrived this morning. I installed it and all of the seg faults are gone. I've learned my lesson. Next time, I will assemble my own machine! Thanks again for all the help. Stephen R. Besch