vicidial.org

Almost everytime I go into Phase 2 after doing the update and reboot I start vicibox-install and after I choose my settings I get "Configuring DataBase Server pre-requisites no crontab for root"
&
"Configuring Web Server pre-requisites
sed: can't read default-server.conf: No such file or directory"

after it completes the install asterisk isn't starting, after you start it asterisk can't find conferences.... all sorts of issues.
I have tried VICIbox 64-bit Standard 3.1.15 & 3.1.13 and I get the same errors... even tried new cd's.... any ideas?

just tried the Preloaded CD too and same thing... when I try the 32 bit version it just scrolls errors....

This is killing me, I even tried a new drive! I've downloaded several copies from 64bit 3.1.13 to 3.1.15 to 32bit 3.1.13 to 3.1.15 and also Preloaded 3.1.13 & 3.1.15... always with the same error message:
I choose
y OS UPdate
y Stop Firewall
y Use SVN Code
y install Database
y install Web Server
y install Telephony
n additional server
n install wanpipe
n install voicetime
********
Then everything starts and I start getting the errors
Updating SVN
Updating OS (This may take a while)...
Configuring general pre-requisites
Configuring DataBase Server pre-requisites
no crontab for root
Configuring Web Server pre-requisites
sed: can't read default-server.conf: No such file or directory
Configuring Telephony pre-requisites
insserv: script vicidial is not an executable regular file, skipped!

I have not installed that iso. However the issue almost sounds hardware related, as a scrolling screen would suggest. But rather than guessing what the issue is, I can only suggest a few things.

1. run a MD5 Check sum on the downloaded iso(s) to verify download is complete.
2. verify system specs meet the minimum requirements
3. Use a different CD burner, or a usb drive.
4. Run memtest on the system
5. try installing from iso onto a virtual machine, and or from the cd-rom.

Hope that helps a little, let us know how the progress is going.

Scrolling screen only happened when I tried the 32-bit version, and once... haven't seen that again. I've now tried several hard drives with the same result, swapped out the ram and tested it good, tried the install with absolutely no internet, no updates and it still gives same error message. I checked the checksum and it matches up, trying a different media form. I've been using CD-R's from memorex and now I'm trying it on a DVD burned from a different utility... who know's

Indeed, I can't rely on my laptop cdrom any more to burn DVD iso. 1% error each disk.. CDs I get 80% success of a 100% burn.

Not sure it would help at all, but try disabling CPU caching in the BIOS, perhaps any other caching.

What are the specs of the machine are you installing to?

Working on this:
Motherboard: A780L3G
Memory: 8GB DDR3
CPU: AMD Phenom II X4 955 (Quad core 3.2GHz)
HD: WD5000AAKS (500 GB 7200RPM)Serial ATA

Previously had Vici 3.1.10 on it, tried OSDial and now that I'm trying to go back... this is where I'm stuck.

Has ANYONE ran into this? I just tried downloading the Standard version 3.1.15 64 bit, sum checked fine and burned on a tower pc, different media....
built another quick server:
MSI G41M-P26 motherboard
Intel Core2 Quad Core Q660 2.4GHz
Kingston 8GB HyperX Blue DDR3-1333MHz
Seagate Barracuda 7200 RPM 250GB HD
and again, same exact problem.
I load the CD, set the network settings, instal os (os-install), do zypper refresh && zypper up
download and install all updates, reboot, run update again... nothing to do so I move on:
vicibox-install
OS Update: y
Stop Firewall: y
Use SVN: y
Install Core DB: y
Install Web App: y
VTiger: n
Install Telephony: y
additional: n
wanpipe: n
voicetime: y
Gives me:
Configuring general system
Configuring Firewall
--good--
Updating SVN
Updating OS
Configuring Database Server pre-requisites
no crontrab for root
Configuring Web Server pre-requisites
sed: can't read default-server.conf: No such file or directory
Configuring Telephony pre-requisites
insserv: script vicidial is not an executable regular file, skipped!

What is going on?!?! I've tried so many new downloads, so many forms of media, now two different computers... no idea, ANY help

I step into "sed: can't read default-server.conf: No such file or directory " every time I install vicibox, but actually I cannot see any issue while they're working.

When I do a screen -list I have 0.....

Didn't think I'd be back on this posting but here it is again:




Could it be hardware? I try it without installing the USB Timing and get the same exact errors. This is off a freshly downloaded copy of ViciBox_Redux.x86_64-3.1.15.iso today.

Would U like some help?

lol, yeah...

Same issue here, already tried a chmod 777 on etc/initd/vicidial with no change in the installation errors. The file wasn't marked executable initially. Used ViciBox_Redux.x86_64-3.1.15.iso

You who have this problem,
can you put some effort into it and write down the exact steps you take when installing (detailed please)

1. Set up RAID 0 in Bios (Supermicro X8-DVL Board), Intel Codebase for RAID
2. Boot server with 3.1.15 x86-64 ISO burnt to CD
3. Do pre-install. Accepting terms and conditions. Allocating IPs. No anomalies here, able to ping internal and external.
4. Run os-install. Accept the prompt for md-raid compatibility. Proceed as normal, local authentication for login. No anomalies here.
5. Reboot server.
6. run zypper refresh && zypper up
7. Run vicibox-install. Have same issues as described (including screenshots above). Have a voicetime usb module as well.

The setup I've chosen is as follows:

OS Update : y
Stop Firewall : y
Use SVN Code : y
Install Core DB : n
Install Web App : y
- Install VTiger : n
Install Telephony : y
- Additional Server : y
- Install Wanpipe : n
- Install Voicetime : y

8. Reboot again
9. From the web interface perform a "Rebuild conf files" on the new server in the cluster, wait 5 minutes. Reboot again.

I have other servers running already with success (1 DB, 1 Archive, 3 Dialler/web), this server is an additional server in the cluster. After reboot the vicidial file in etc/init.d is still not marked executable. I chmod'd it again and after another reboot seems to remain executable.

However, after reboots asterisk still isn't starting up as intended and you have to rectify this with a
safe_asterisk
/etc/init.d/dahdi restart
dahdi_cfg -vvvvv
and in the asterisk cli : module reload chan_dahdi.so

every time

Ok, so your problem is that dahdi aint autostarting. run:
chkconfig dahdi
if it is off you need to:
chkconfig dahdi on

what permissions did /etc/init.d/vicidial have before you run chmod 777?

And yeah you can look in your /var/log/vicibox.log file too, post it if you find any errors

and the original error this thread was about "sed: can't read default-server.conf: No such file or directory"
thats not so strange when I took a look at it, the code:

Code: Select all

  # Make the default permissions include indexes for Matt's audio store
  cd /etc/php5/conf.d
  sed -i 's/Options None/Options Indexes/' default-server.conf


the md5sum of the script too tell the version (because it aint got a version-number)
a227b926512edcaf7f344d58cb6e7869 /usr/local/bin/vicibox-install

there are no default-server.conf file in /etc/php5/conf.d/
it is located here:
/etc/apache2/default-server.conf
patch:

Code: Select all

-  cd /etc/php5/conf.d
+  cd /etc/apache2

but its not a serious error, vicidial should work anyway

Thanks Domedan, the non-working /etc/init.d/vicidial file has 644 permissions before modification.

The dadhi configuration worked a charm and the server now properly remembers that config after reboots, however the vicidial service still fails to start. Just added a

service vicidial start

Command to the /etc/init.d/boot.local file and we're happy.

Happy to report that your patch also solved the initial sed issue, just modified the vicibox-install script and we didn't have that error on subsequent installs.

Ok weird, should be 755 permission on that file, dont know what could have caused that.
so dahdi starts up after you have done "chkconfig dahdi on"

regarding vicidial, you can do:
chkconfig vicidial
to check if that service is on (starts at boot), if its off then you can enable it with:
chkconfig vicidial on
just as dahdi, and then you can remove the command you wrote in /etc/init.d/boot.local

this should have been done by vicibox-install script though:

Code: Select all

if [ "$VICISERV" == "y" ]; then
...
  # Make sure everything starts for us on reboot :)
  chkconfig apache2 on
  chkconfig vicidial on
  /etc/init.d/apache2 restart >> /var/log/vicibox.log  2>> /var/log/vicibox.log


and $VICISERV was y when you run the script:

Code: Select all

choice "Will this server be used as a Telephony server? (y/N) : "
VICISERV="$CHOICE"


It would be interesting too see whats happening when you run the script.
can you post your /var/log/vicibox.log ?

it wont show everything but its a start.
if that wont help, you can do this:
bash -x /usr/local/bin/vicibox-install

its kind of hard to tag along though, and to save all output to a file you can do this:
script -c "bash -x /usr/local/bin/vicibox-install" vicibox_output.txt
so you later on can look in vicibox_output.txt, or post it for someone else to examine

Today I tried a fresh install and the only error I got was no cron tab for root while configuring database server perquisites on ViciDial 4.0 beta2.
This gives me no 6666 access when trying to log into the dialer and when I check my screens I only see 8:

Code: Select all

There are screens on:
        2162.ASTfastlog (Detached)
        2159.ASTVDremote        (Detached)
        2156.ASTVDauto  (Detached)
        2153.ASTlisten  (Detached)
        2150.ASTsend    (Detached)
        2147.ASTupdate  (Detached)
        2051.asterisk   (Detached)
        2033.astshell20120812100232     (Detached)
8 Sockets in /var/run/screens/S-root.


Which screen am I missing and if I did a restore of a previous database would it fill in correctly?

you are discussing several entirely unrelated items. let me elaborate:

1) "no crontab for root" is not an error, per se, but merely an observation. After the system notes that there isn't one (which makes sense as the system has just been installed), it creates one. If you log in via ssh (as root of course) and enter "crontab -e", you will note that there is not a crontab and it has the stock vicidial entries in it. Thus, this is not an error and nothing is wrong here. Next.

2) No 6666 access is not entirely descriptive of a problem, but I will assume that you cannot log in as 6666 via a web page on this server. Your description contains no technical details so I'll guess a few times: ( a ) No web server installed: If this is truly a DB only server, apache isn't even running. You'll want to log in to the web server of the cluster instead of the DB server. ( b ) You can see the Welcome page, but when you click on "Administration" and are asked for security (user/pass), your user/pass do not allow you access. There could be several reasons for this such as the wrong user/pass and/or a misconfigured DB connection. Elaborate on your actual problem and we'll help you through it.

3) 8 Screens is normal if you have set the keepalives to the appropriate number of requested screens in astguiclient.conf (which is created by the Q/A section during the build of the server).

Summary: Are you installing a DB server for a cluster or a standalone machine with db/web/dialer all in one? What precisely is the description of the problem with the login?