I've moved 1 of our facilities over from 1.2 to 1.4 two weeks back. So far, the only issue that I've encounted is. I have a scheduled CRON job that runs at 3am every Sunday, that issues a: asterisk -rx 'restart when convenient' The first Sunday that it ran, Asterisk never restarted. The CRON logs show that it issued the command successfully. This Sunday, it ran but never started back up. Anybody else encountered this? Doug
Doug Lytle wrote:> I've moved 1 of our facilities over from 1.2 to 1.4 two weeks back. So > far, the only issue that I've encounted is. > > I have a scheduled CRON job that runs at 3am every Sunday, that issues a: > > asterisk -rx 'restart when convenient' > > The first Sunday that it ran, Asterisk never restarted. The CRON logs > show that it issued the command successfully. This Sunday, it ran but > never started back up. > > Anybody else encountered this?MANY CLI commands changed from 1.2 to 1.4. They should be all documented in the 1.4 upgrade and changes documents. In 1.2 the upgrade document was called UPGRADE.txt. You might want to look at that, in addition to the 1.4 UPGRADE.txt, as there are many features that were deprecated in 1.2 that were remove din 1.4
Eric "ManxPower" Wieling wrote:> Doug Lytle wrote: > > document was called UPGRADE.txt. You might want to look at that, in > addition to the 1.4 UPGRADE.txt, as there are many features that were >The document was reviewed and the appropriate changes to the dial plan were made. I found no reference to the command being changed. I does work if run manually, running on a schedule is where it seems to be a little flaky. Doug -- Ben Franklin quote: "Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety."
Doug Lytle wrote:> Eric "ManxPower" Wieling wrote: >> Doug Lytle wrote: >> >> document was called UPGRADE.txt. You might want to look at that, in >> addition to the 1.4 UPGRADE.txt, as there are many features that were >> > > > The document was reviewed and the appropriate changes to the dial plan > were made. > > I found no reference to the command being changed. I does work if run > manually, running on a schedule is where it seems to be a little flaky.Sorry, I figured the command was changed to "core restart when convenient", but I have discovered that it was not, in fact, changed.
Eric "ManxPower" Wieling wrote:> Doug Lytle wrote: >> Eric "ManxPower" Wieling wrote: >>> Doug Lytle wrote: >>> >>> document was called UPGRADE.txt. You might want to look at that, in >>> addition to the 1.4 UPGRADE.txt, as there are many features that were >>> >> >> The document was reviewed and the appropriate changes to the dial plan >> were made. >> >> I found no reference to the command being changed. I does work if run >> manually, running on a schedule is where it seems to be a little flaky. > > Sorry, I figured the command was changed to "core restart when > convenient", but I have discovered that it was not, in fact, changed.See http://bugs.digium.com/view.php?id=8925 for a list of all commands in 1.4 that were not converted to the new 1.4 syntax.
Quoting Doug Lytle <support at drdos.info>:> Anybody else encountered this?I have. But i did it manually, not from a cron job... It didn't restart for me either... I had to resort to a full restart with the init script... -- PLO toluene SEAL Team 6 supercomputer president DES Waco, Texas Cocaine NSA Soviet bomb ammonium Clinton smuggle AK-47 [See http://www.echelonwatch.org/ for more about this] http://www.theregister.co.uk/2001/09/06/eu_releases_echelon_spying_report/ http://www.aclu.org/safefree/nsaspying/23989res20060131.html#echelon