vicidial.org

by **Kumba** » Wed Sep 08, 2010 10:56 pm

Version 3.0.1 of ViciBox Redux and DB released. Contains these bugfixes:

- Changed the default partitioning to 4-gb swap and rest as root
- Added findutils-locate package
- Updated to use SVN v.2.4-279 Build 100908-0926

Here are the links:

http://download.vicihost.com/iso/vicibo ... -3.0.1.iso

http://download.vicihost.com/iso/vicibo ... -3.0.1.iso

by **Kumba** » Fri Sep 10, 2010 11:48 pm

Version 3.0.2 of ViciBox Redux and DB released. Contains these bugfixes:

- Corrected a typo in the partitioning scheme; Will now put both partitions (root and swap) on the same disk by default
- Specified swap specifically as type 'swap' format, corrects it ending up as EXT4

Enjoy.

http://download.vicihost.com/iso/vicibo ... -3.0.2.iso

http://download.vicihost.com/iso/vicibo ... -3.0.2.iso

by **williamconley** » Sat Sep 11, 2010 8:33 am

Sounds like you are zeroing in on it

by **Kumba** » Sat Sep 11, 2010 7:27 pm

Version 3.0.3 of ViciBox Redux and DB released. Contains these bugfixes:

- Changed the dialcron to compress to MP3 instead of GSM
- Added utility to enable FTP transfer cronjob for multiserver

by **williamconley** » Tue Sep 14, 2010 4:56 pm

Is there a specific location during installation (log file, astguiclient.conf ...) where the version of the installer is recorded officially?

If not ... can we add one?

I mean, the .iso version (so a client system could be DUPED without question)

the only variable then being that the OpenSUSE distro may change some details during OS installation.

This could also be helpful for later troubleshooting (yes, I have clients who "forget" which .iso they installed with, so if there's a problem i have no way of linking it to a specific distro). Obviously going back and adding this would not be worthwhile, but going forward ... it could come in very handy.

Personally, I think an installation log would be good. Restrict entries to specifically "os-install", "vicibox-install" and if you wanted to be funny, install.pl activation (which would record the svn version information ... so that one could easily identify which versions were installed and in what order).

Happy to add it to the tracker, but wanted to see if it was worthy (or already considered and enacted or discarded)

It would even be nice if the astguiclient.conf and extensions.conf had a version number (from the svn) installed.

by **Kumba** » Thu Sep 16, 2010 11:50 am

When you login to the system as root, it's displayed in the MOTD as the very last line automatically.

Says something like "ViciBox Redux v.3.0.4".

There is already a vicibox logfile created at /var/log/vicibox.log

by **Trying** » Thu Sep 16, 2010 11:53 am

I think the command to install the DB in the clustering documentation should be vicibox-db and not vicihost-db.

by **Kumba** » Thu Sep 16, 2010 2:57 pm

Corrected the typo and uploaded new documentation.

by **williamconley** » Fri Sep 17, 2010 7:35 pm

Kumba wrote:Says something like "ViciBox Redux v.3.0.4".

egads: ViciBox Redux v.3.0.0, you're right! (I was looking at an earlier box just said "2.0" instead of full .iso version) Handy

There is already a vicibox logfile created at /var/log/vicibox.log

And so there is ... but ...

I was thinking something more along the lines of "package installed", and "svn upgraded to ..." that sort of thing, not so much "scour the output for errors" (although that is OBVIOUSLY a requirement and very handy to have now).

Just a thought.

by **Kumba** » Fri Sep 17, 2010 8:10 pm

I guess I'm not understanding what you are asking or suggesting.

You can use zypper/yast to see what packages are installed.

You can also type svn info to see what SVN code they used when last installed, and compare that to the db schema version. Everything else has to match this anyways.

If someone installs something from source then you are just kind of on your own, like any other linux OS.

Beyond that, I'm really not too sure what else there is to track.

by **williamconley** » Fri Sep 17, 2010 8:41 pm

I've had some situations where knowing which versions of VICIdial have "passed through" has come in handy, but i've had to get it from "History".

The concept would be ... each time any Vicidial software is installed or modified, a single line entry in a "dialer installation log" (not a huge text file, just a one line of "install of VICIdial v. 2.4 build XXXX on this date and time").

So I guess the request would be to have the install.pl file store a 1-5 line "here's what I did today" in a VICIdial_version.log.

This would also be handy for the mysql table changes, but since those are expected to be run from the command line directly there would have to be a wrapper that runs it instead (to say "upgrade_2.0.5.sql" run 2010-09-15).

This would be moderately handy to get into a client's box and find where they are when they don't know, which happens a surprisingly lot. LOL In the end it would be possible to "look at the dialer log" (or VICIdial.log) and see the "growth" of the system. If a particular issue arises ONLY if upgrading through a certain path, this could expose the flaw. SVN could contain some of this information, but does not track "install.pl" execution.

Ok, I babbled a bit, but i hope I got it across.

by **Kumba** » Fri Sep 17, 2010 9:09 pm

That's not related to ViciBox. That would be something to be done by the ViciDial code itself. You would need to talk to Matt about that.

ViciBox is related only to the OS Installation, and correct set-up of the software. Changes to the core software code itself is not within scope of ViciBox.

I would try posting your request in the Features section.

by **williamconley** » Fri Sep 17, 2010 9:29 pm

Valid. Thanks, would it be possible (if i get matt onboard) for ViciBox to "initiate" the sequence (as in, plop the "base install" information into said file?

)

this would be similar to the www.Vicibox.com site "specs section" so users would have a single location to see what just landed on their server (related to the Dialer installation ... of course ...)

Yes, I know I'm annoying.

by **Kumba** » Fri Sep 17, 2010 10:10 pm

Version 3.0.4 of ViciBox Redux and DB released. Contains these bugfixes:

- Updated to SVN v.2.4-280 Build 100912-0842
- Applies new updates from OpenSuSE
- Install Documentation corrected and verified by this build

Here are the links:

http://download.vicihost.com/iso/vicibo ... -3.0.4.iso

http://download.vicihost.com/iso/vicibo ... -3.0.4.iso

by **Kumba** » Mon Sep 20, 2010 11:10 pm

Release 3.0.5 is here. Include these fixes:

- Upgraded wanpipe to v.3.5.15 to correct a kernel compat issue
- Changed wanpipe compilation method per Nenad at Sangoma
- Changed kernel from 'default' to 'pae' config to keep config consistency in future revisions
- Changed the dahdi init script removal process to be more proper
- Adjusted asterisk-recompile to include the above changes

by **Trying** » Tue Sep 21, 2010 7:22 am

This is pretty cool. Every time I download your latest release and just as I want to start installing you bring out another release

by **williamconley** » Tue Sep 21, 2010 3:10 pm

http://download.vicihost.com/iso/vicibo ... -3.0.5.iso

thanks, I'm downloading now. Have a new server to build tomorrow.

by **Kumba** » Tue Oct 05, 2010 12:41 am

Version 3.0.6 of ViciBox Redux and DB released. Contains these bugfixes:

- Updated to SVN v.2.4-283 Build 100929-1203
- Applies new kernel updates from OpenSuSE
- Fixed a missing pipe resulting in extra output to the CLI

Here are the links:

http://download.vicihost.com/iso/vicibo ... -3.0.6.iso

http://download.vicihost.com/iso/vicibo ... -3.0.6.iso

by **williamconley** » Tue Oct 05, 2010 6:38 pm

i note a minor issue regarding phpmyadmin. no root mysql password = no functionality of phpmyadmin. if this hasn't been fixed in the "latest", it would be nice to set the root mysql password during installation.

ask the user what to set it to, and then:

Code: Select all: mysql asterisk --execute="UPDATE mysql.user SET Password=PASSWORD('XXXX') WHERE User='root';" mysql asterisk --execute="FLUSH PRIVILEGES;"

while we are at it: a prompt for the location of the web root forward would be pleasant.

I do not like the bounce advertising the presence of a freshly installed phone dialer. Makes more sense to allow the installer to (optionally) point it anywhere they like such as their corporate home page.

by **phil_discount** » Tue Oct 19, 2010 4:20 am

i don't know if there is a problem of mysql or little installation problem.
many people have this problem (google) with mysql and i found only one solution in forums -> reinstall mysql

my.cnf
long_query_time = 3
slow_query_log
slow_query_log_file=/var/log/mysql/log-slow-queries.log

during start mysqld.log reports:

Code: Select all: /usr/sbin/mysqld: File '/var/log/mysql/log-slow-queries.log' not found (Errcode: 13) 101018 22:50:49 [ERROR] Could not use /var/log/mysql/log-slow-queries.log for logging (error 13). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.

i created manually the file with touch log-slow-queries.log and give the file the correct user/group and rights which mysql needs.

does anybody else have this problem?
i done three installations on three different machines, everytime the same problem.

regards
philip

by **williamconley** » Sat Oct 23, 2010 6:15 pm

at what stage does this error occur, is it in a log or on the CLI?

does it remain AFTER full installation? (many things are not quite complete during installation, but does this issue survive a reboot ?)

i've never noticed this error on one of my boxes ... nor does "log-slow-queries" appear anywhere in the log folder ... so there doesn't seem to be an error tossed with that string in it ...?

by **phil_discount** » Thu Nov 11, 2010 3:08 am

the logfile is placed in /var/run/mysql/mysqld-slowquery.log ...
i receive the "error" only during start of mysql in the logfile.
but slow query works, only the directory is wrong the the message in log.

by **Kumba** » Sun Nov 21, 2010 7:11 pm

Version 3.0.7 of ViciBox Redux 32-bit and new 64-bit released. Contains these bugfixes:

- Created a completely 64-bit version of ViciBox Redux per sponsor
- Deprecated the database-only build, just use the 64-bit Redux version
- Updated to use SVN v.2.4-288 Build 101115-135
- Upgraded Sangoma Wanpipe to v.3.5.17 (for good measure)
- Upgraded libPRI to v.1.4.11.4 (per bug report on forum)
- Added optimizations to Apache when used as a dedicated web server (per bug report)
- Added large database optimizations prompt when used as a dedicated DB server (per forum request)
- Added SSHFS, PHP5-XSL per development sponsor

Here are the links:

http://download.vicihost.com/iso/vicibo ... -3.0.7.iso

http://download.vicihost.com/iso/vicibo ... -3.0.7.iso

by **williamconley** » Sun Nov 21, 2010 7:16 pm

Any likely issues with the 64-bit install version?

I will probably test that tomorrow.

by **Kumba** » Sun Nov 21, 2010 7:31 pm

Not that I know of. I tested it about a dozen times through all the options. But that doesn't mean there's not some combination of options that doesn't work.

That's where the community comes in. Let me know any bugs you all find.

by **Trying** » Mon Nov 22, 2010 8:23 am

Hi

I am busy with installation and notice there is no option to install VTiger on the DB only installation. Also on the vicibox-install page the included snapshot is v 2.4-279 build 100908-0926.

by **Trying** » Mon Nov 22, 2010 8:41 am

I also get "Could not install Sangoma Wanpipe drivers" on all 4 of my dialers. I am using the 64bit disc to install on all servers.

by **josh1856** » Mon Nov 22, 2010 11:30 am

What is the upgrade process for and existing version Vicibox?

by **williamconley** » Mon Nov 22, 2010 1:16 pm

at the top of this screen click on "Vicidial wiki", then look for "SVN How To"

that's one method

another method is to just download the new vicidial source code package and read the UPGRADE.txt file included in each download. that will give you step by step instructions for upgrade from any version to the next higher version (so you can upgrade one step at a time to latest or stop anywhere you like).

the best thing about SVN, by the way, is that the first step just downloads the entire package (whichever version you selected) without installing anything, thus giving you immediate (commitment freeeee!) access to that same UPGRADE.txt file.

by **Kumba** » Tue Nov 23, 2010 3:36 am

If you are already running ViciBox v.3.0 and everything works, then there isn't much benefit to reloading the OS. If you want to just update the vicidial code then use the methods already presented. They work pretty good and are a lot less of a headache then a fresh install.

You no longer need (or should) use the DB-Only installer. It will not be maintained going forward. If you install ViciBox Redux as a dedicated database, it will ask you if you want to use a large MySQL optimized config file. This serves as the replacement for the DB-Only installer. Otherwise it uses the default MySQL config that came with the regular ViciBox, which is decent for most small cluster setups (I.E. below 75 agents). You can optionally copy this large config file from /usr/src/astguiclient/conf/my-bigvici.cnf to /etc/my.cnf if you want to get the bigger config. Read the comments at the top of this file before blindly copying it over. Failure to do so could result in a borderline unfunctional cluster!

The VTiger installation is a subset of the Web Server. The VTiger database is installed by default on any server selected with the DataBase role. The old functionality of the DB-Only install was to provide Database and Web roles. Since ViciBox Redux DB-Only is no longer being supported, that functionality is gone as well.

The only primary installation difference between 32-bit and 64-bit ViciBox Redux is that the 64-bit has an optional "Large MySQL Optimization" for ViciDial. This option is only presented when the 64-bit server is installed as a stand-alone DataBase. The 32-bit version does not have this optimization as it cannot support it properly.

I'll be releasing v.3.0.8 to include these fixes:
- Wanpipe compilation issue on 64-bit
- SVN code version in vicibox-install

by **Kumba** » Tue Nov 23, 2010 5:18 am

Version 3.0.8 of ViciBox Redux 32-bit and new 64-bit released. Contains these bugfixes:

- Fixed wanpipe compilation issue on 64-bit
- Corrected the vicibox-install to display the correct SVN code revision

http://download.vicihost.com/iso/vicibo ... -3.0.8.iso

http://download.vicihost.com/iso/vicibo ... -3.0.8.iso

by **Trying** » Tue Nov 23, 2010 6:37 am

I see keepalives 5,7 and 9 are defaulted on the DB only installation. Is this correct or should it rather be on one of the Asterisk servers? I saw somewhere that Matt suggested a DB only server should be set to X? What about a web server? Should that also be set to X?

by **williamconley** » Tue Nov 23, 2010 9:43 am

http://www.poundteam.com/downloads/Vici ... v1%201.pdf

by **Trying** » Tue Nov 23, 2010 9:57 am

I have that document William. I actually paid for it's development.

I am just wondering why Kumba has it set up like that as defaults on the Vicibox distro.

by **williamconley** » Tue Nov 23, 2010 10:34 am

having the db server run scripts is a matter of power balancing. if you have a powerful db server, and it CAN run the scripts ... excellent. as long as they are scripts that deal with DATA.

by **Kumba** » Tue Nov 23, 2010 2:01 pm

Any scripts that are global to the proper functioning of ViciDial are run from the database. This include keepalives 579, the Hopper, and a few other things ran from cron. The resource load of these things is minimal on most dedicated databases when compared to what MySQL is going to chew up.

The reason why this design decision was made is so that downtime of a web server, or dialer, doesn't effect the rest of the cluster. Since ViciDial is so database-centric, this made the Database the proper place to run such critical things.

Basically, if your database goes down, nothing else is going to work anyways. And the same goes for these keepalive and cronjobs. All the more reason why I try to explain to people NOT to go cheap on the database. It is literally the core of everything in ViciDial.

If you have one database server with multiple ViciDial instances on it, then you don't have much of a choice other then to move these requirements to the dialers.

by **Kumba** » Wed Dec 01, 2010 12:51 am

Version 3.0.9 of ViciBox Redux 32-bit and new 64-bit released. Contains these bugfixes:

- Upgraded Wanpipe Voicetime to v.1.0.9.1 courtesy of Sangoma
- Upgraded SVN snapshot to v.2.4-290 Build 101127-2232
- Applied new kernel patch update 0.5.1 (for potential issues on forum)
- Added php5-xmlrpc and php5-pear for QueueMetrics Integration
- Added some Adaptec and LSI SCSI firmwares from repositories (for potential issues on forum)
- Added an option to ignore errors in upgrade_2.4.sql, fixing the SVN Update bug (that some head-developer made!!!)
- Updated repositories and applied new updates
- Added sysstat package for I/O troubleshooting
- Added libcurl-devel per client request

http://download.vicihost.com/iso/vicibo ... -3.0.9.iso

http://download.vicihost.com/iso/vicibo ... -3.0.9.iso

by **mflorell** » Wed Dec 01, 2010 7:14 am

Hey, that bug is in there on purpose

It has to do with older versions of MySQL not deleting the PRIMARY KEY unless you specifically run that query or drop the table. The newer versions are not affected, which is why you get the error.

Of course, if you use the MySQL_AST_CREATE_tables.sql file like you should be doing on a new install you wouldn't have had this problem

by **Trying** » Wed Dec 01, 2010 8:03 am

I am a happy man!! The installation went smooth!! No issues!!

by **Kumba** » Wed Dec 01, 2010 2:07 pm

It's ok, I patched around your bug.

vicidial.org

ViciBox Redux v.3.0.9 Released

ViciBox Redux v.3.0.9 Released

Upgrade Process

Who is online