Missing crons

[GaD]

Hi all!
I recently installed a new cluster of Vicis with Vicibox5. We're doing the database on a MariaDB cluster that we already have, and the WEB on a WEB server that we're barely using right now. I took a server and threw the Vicibox installer and ran the 'This is a telephony server = Y' when I was asked for the options during installation. The server SQLd itself in the database fine, no problems there, but the box itself did not install the '-vici' files in /etc/asterisk (like extensions-vici.conf). I downloaded the latest SVN (again, I had done so at installation time) and ran install.pl which pretty much fixed the issue.

Now I have a funny problem. Root's crontab is empty, like..... EMPTY! So..., I believe that inside the SVN checkout of 'trunk' there is a directory called 'config' where I found part of the respective cronstab files. At this point I want to ask the question..., are those the current crons for this install of Vici (Vicibox5 installerVERSION: 2.8-415a BUILD: 131007-1234) ? And secondly..., is this normal that my install went 'through' without the crons and the -vici files??

Thanks 'yall!

[williamconley]

Some challenges to your theories:

1) The installer does not need to install "xxxxx-vici.conf" because those are generated by the vicidial scripts later. So those being "missing" is not an indication of a problem. Sorry.
2) Since it likely took you more than a couple minutes to svn and install again, the timed operation likely created those files without the install.pl having anything to do with it. (FYI)
3) You would probably benefit (greatly!) from a Virtual installation of a cluster. vSphere or VMWare or Virtualbox is great for this. Then you can install to your heart's content without even moving from your desk (no CDs to put in/take out) and you can Snapshot at any given moment for a place to go back to in case your next phase messes up. IE: Install the OS and save ... then also save the DB server ... then install the dialer a dozen times until you're happy with the outcome. Even a virtual cluster can handle a single agent, so when you're done it's easily tested.
4) Did you check the vicibox.log (made by the installer) to see ... what happened? Ordinarily if the install fails, there will be an error in the log at the moment of failure and everything from that moment to the end of the install script must be executed (we just start over, though, no risk of a dirty install!).

Happy Hunting!