eAccelerator question

[pandora]

Hi guys,

I'm a noob in Ubuntu and VICIdial. I installed these for additional knowledge I used VMware for this (I won't use it for production!)
I used the VICIdial Ubuntu installation guide in the wiki - VICI:Ubuntu Install. I used Ubuntu 12.04.4. Anyway, I am having problems with eAccelerator. I can download the eAccelerator without any problems, but when I use unzip, the terminal says that it can't find the path or it can't find eaccelerator. Is it a compatibility issue or I did something wrong?

Thanks for the help in advance!

[williamconley]

Why are you installing manually? (Posting why often helps us understand your situation ... because you SHOULD be installing via Vicibox.com's iso installer!)

eAccelerator is not part of Vicidial. It is a module designed to speed up Apache. It has its own support pathway. Also: for a "test server", you don't really need it.

I will also say that if you cannot unzip a downloaded file ... you probably should look at using an iso installer to build your system. Just sayin' ...

ALL that being said, if you contact me outside the forum, we may enlist you in our Alpha release of Vicidial on Ubuntu (which may resolve your Ubuntu installation issues, including eAccelerator). Especially if you're looking for a dev box instead of a production box right now. We'd be interested in your experience with it.

[pandora]

Hey! Thanks for the reply.

Well, I'm installing it manually 'cause I want to start from scratch (the experience and all).

They said any distro would work, as long as it's from a linux kernel, so I picked Ubuntu (which I already have).

So... I might try and download the one in Vicibox or.. oh, now, that I've thought about it.. I downloaded the eAccelerator manually, extracted the file in the downloads folder and used the mv command. So, by doing this, I thought that I solved the problem in extracting the tar.gz, but I was wrong! When I do ./configure, it doesn't say any thing, so I assumed nothing bad happened. So, I went on end entered make and make install and the errors are there.

Since, eAccelerator isn't that important, I could skip the part. I will post the outcome after I've finished everything!

Thanks!

[geoff3dmg]

You should get a lot of output from running ./configure (regardless of what you are trying to compile). Did you do 'apt-get install build-essential'? As that installs the full compile toolchain on Ubuntu.

[pandora]

Hi geoff3dmg,

Yeah, I did every step in the guide that is found in the wiki. I could try it again and post the output.

[geoff3dmg]

Yes, post your ./configure output.

[pandora]

Hi,

Here's the output for apt-get install build-essentials:

Code: Select all

Reading package lists... Done
Building dependency tree       
Reading state information... Done
build-essential is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

BTW, sorry about the ./configure output which I told you guys that I didn't receive any, where in fact I did (forgetfulness?). Anyway, here's the output for ./configure under /usr/src/eaccelerator-0.9.5.3:

Code: Select all

checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for a sed that does not truncate output... /bin/sed
checking for cc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking how to run the C preprocessor... cc -E
checking for icc... no
checking for suncc... no
checking whether cc understands -c and -o together... yes
checking for system library directory... lib
checking if compiler supports -R... no
checking if compiler supports -Wl,-rpath,... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for PHP prefix... /usr
checking for PHP includes... -I/usr/include/php5 -I/usr/include/php5/main -I/usr/include/php5/TSRM -I/usr/include/php5/Zend -I/usr/include/php5/ext -I/usr/include/php5/ext/date/lib
checking for PHP extension directory... /usr/lib/php5/20090626
checking for PHP installed headers prefix... /usr/include/php5
checking if debug is enabled... no
checking if zts is enabled... no
checking for re2c... no
configure: WARNING: You will need re2c 0.13.4 or later if you want to regenerate PHP parsers.
checking for gawk... no
checking for nawk... nawk
checking if nawk is broken... no
checking whether to enable eaccelerator support... yes, shared
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for unistd.h... (cached) yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sched.h usability... yes
checking sched.h presence... yes
checking for sched.h... yes
checking mandatory system headers... yes
checking whether union semun is defined in sys/sem.h... no
checking for sysvipc shared memory support... yes
checking for mmap shared memory support... yes
checking for mmap on /dev/zero shared memory support... yes
checking for anonymous mmap shared memory support... yes
checking for posix mmap shared memory support... no
checking for best shared memory type... anonymous mmap
checking for spinlock semaphores support... yes
checking for pthread semaphores support... no
checking for posix semaphores support... no
checking for sysvipc semaphores support... yes
checking for fcntl semaphores support... yes
checking for flock semaphores support... yes
checking for best semaphores type... spinlock
checking for sched_yield... yes
checking for mprotect... yes
checking for ext/session/php_session.h... yes
checking how to print strings... printf
checking for a sed that does not truncate output... (cached) /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by cc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking for gawk... (cached) nawk
checking command to parse /usr/bin/nm -B output from cc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if cc supports -fno-rtti -fno-exceptions... no
checking for cc option to produce PIC... -fPIC -DPIC
checking if cc PIC flag -fPIC -DPIC works... yes
checking if cc static flag -static works... yes
checking if cc supports -c -o file.o... yes
checking if cc supports -c -o file.o... (cached) yes
checking whether the cc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating ./config.status
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing libtool commands


[williamconley]

While the "install experience" may seem like a good idea, you may want to consider using the .iso installer and then performing a parallel installation in OpenSuSE so your iso install matches the "real" installation perfectly. Then any problems you have can be tracked to the installation script designed to work in the same OS.

But I would say that rebuilding this wheel is not entirely worthy. You have a lot of work ahead (a fairly hefty learning curve) learning Vicidial itself. If you use the .iso installer, you can move on to that and "consider" all the OS implications on a live, running system. And perhaps later you can look back at all the components in the system with that (already have one running) perspective.

In the end, when upgrades happen, they are vetted by a very large community of users ... all in OpenSuSE (and a small group of CentOS users with Goautodial which is another Vicidial installation iso).

So my advice would be ... ISO install now and work out manual installation in an opensuse box in parallel if you must have this information (which is prudent to be sure you can manage the system in real time in the future regardless of what happens). This will give you a nice comparison between a live, running system and your manual build box. Unless you like "the hard way". LOL

On the other hand, we do still have our .iso installer alpha for Ubuntu. May be helpful as well. I believe we modified it for MariaDB and Asterisk 1.8.

[pandora]

Thanks for the advice!

I might as well download the .iso and start from there. Well, if you don't mind, can I have the links? Thank you!

[geoff3dmg]

BTW your ./configure looks like it was successful.

[williamconley]

Thanks for the advice!

I might as well download the .iso and start from there. Well, if you don't mind, can I have the links? Thank you!

Vicibox.com

[pandora]

Hey guys..

I have now Ubuntu 8.04-server-amd64.. I did everything in the pdf guide and the basic installation went smooth (username, keyboard, etc). Now, when I type apt-get update, it says Error 404 for hardy-security. I chose Philippines as the country.

Any advice? Thank you!

[williamconley]

advice: Don't try to install an OS that is several years old and expect it to go smoothly.

[pandora]

advice: Don't try to install an OS that is several years old and expect it to go smoothly.

I decided to go with OpenSUSE as to avoid any further problems. Anyway, thanks for the help guys! I will post the result again after I finish with the latest installation (the third one).

Thank you very much Sirs *hand salute*

[pandora]

Hey guys!

Good day to you. I have now my own VICI server. Thanks for your help about eAccelerator and the idea (weird, the post admin doesn't want me to post the sug*estion word) to use OpenSUSE or download the one in Vicibox.

I used Vicibox 4.0 Server, running in VMware (no, I am not going to use this for production). The learning starts now. Hope you guys can guide and help me, if I encounter any problems. Thanks again!

[williamconley]

manual is at eflo.net (Vicidial managers manual)

start at page one and don't skip ANYTHING. seriously. work through every page.