Welcome! Log In Create A New Profile

Advanced

PHP-FPM not starting with segment fault error

Posted by DiliBau 
DiliBau
PHP-FPM not starting with segment fault error
April 15, 2010 12:28PM
Basically when I run "php-fpm start" I get Sement fault and that`s
about it regarding error messages.

Here are the last 100 lines of my php-fpm.log

localhost:~# tail -n 100 /usr/local/logs/php-fpm.log
Apr 09 18:41:53.066729 [NOTICE] fpm_got_signal(), line 48: received
SIGCHLD
Apr 09 18:41:53.067041 [NOTICE] fpm_got_signal(), line 48: received
SIGCHLD
Apr 09 18:41:53.067055 [WARNING] fpm_children_bury(), line 215: child
820 (pool default) exited on signal 15 SIGTERM after 4.519846 seconds
from start
Apr 09 18:41:53.067065 [NOTICE] fpm_pctl_exit(), line 81: exiting, bye-
bye!
Apr 09 18:41:53.085166 [NOTICE] fpm_unix_init_main(), line 284:
getrlimit(nofile): max:1024, cur:1024
Apr 09 18:41:53.085384 [NOTICE] fpm_event_init_main(), line 88:
libevent: using epoll
Apr 09 18:41:53.085465 [NOTICE] fpm_init(), line 52: fpm is running,
pid 830
Apr 09 18:41:53.086322 [NOTICE] fpm_children_make(), line 352: child
831 (pool default) started
Apr 09 18:41:53.087201 [NOTICE] fpm_children_make(), line 352: child
832 (pool default) started
Apr 09 18:41:53.087997 [NOTICE] fpm_children_make(), line 352: child
833 (pool default) started
Apr 09 18:41:53.088892 [NOTICE] fpm_children_make(), line 352: child
834 (pool default) started
Apr 09 18:41:53.089565 [NOTICE] fpm_children_make(), line 352: child
835 (pool default) started
Apr 09 18:41:53.089591 [NOTICE] fpm_event_loop(), line 107: libevent:
entering main loop
Apr 09 19:17:40.370628 [NOTICE] fpm_got_signal(), line 56: received
SIGTERM
Apr 09 19:17:40.370665 [NOTICE] fpm_pctl(), line 256: switching to
'terminating' state
Apr 09 19:17:40.371323 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 835 (pool default)
Apr 09 19:17:40.371717 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 834 (pool default)
Apr 09 19:17:40.372082 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 833 (pool default)
Apr 09 19:17:40.372612 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 832 (pool default)
Apr 09 19:17:40.373139 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 831 (pool default)
Apr 09 19:17:40.373150 [NOTICE] fpm_pctl_kill_all(), line 181: 5
children are still alive
Apr 09 19:17:40.373163 [NOTICE] fpm_got_signal(), line 48: received
SIGCHLD
Apr 09 19:17:40.373297 [WARNING] fpm_children_bury(), line 215: child
831 (pool default) exited on signal 15 SIGTERM after 2147.286996
seconds from start
Apr 09 19:17:40.373420 [WARNING] fpm_children_bury(), line 215: child
832 (pool default) exited on signal 15 SIGTERM after 2147.286231
seconds from start
Apr 09 19:17:40.373536 [WARNING] fpm_children_bury(), line 215: child
833 (pool default) exited on signal 15 SIGTERM after 2147.285550
seconds from start
Apr 09 19:17:40.373655 [WARNING] fpm_children_bury(), line 215: child
834 (pool default) exited on signal 15 SIGTERM after 2147.284983
seconds from start
Apr 09 19:17:40.373774 [WARNING] fpm_children_bury(), line 215: child
835 (pool default) exited on signal 15 SIGTERM after 2147.284219
seconds from start
Apr 09 19:17:40.373791 [NOTICE] fpm_pctl_exit(), line 81: exiting, bye-
bye!
Apr 09 19:24:28.685567 [NOTICE] fpm_unix_init_main(), line 284:
getrlimit(nofile): max:1024, cur:1024
Apr 09 19:24:28.685802 [NOTICE] fpm_event_init_main(), line 88:
libevent: using epoll
Apr 09 19:24:28.685895 [NOTICE] fpm_init(), line 52: fpm is running,
pid 31285
Apr 09 19:24:28.686805 [NOTICE] fpm_children_make(), line 352: child
31286 (pool default) started
Apr 09 19:24:28.687676 [NOTICE] fpm_children_make(), line 352: child
31287 (pool default) started
Apr 09 19:24:28.688492 [NOTICE] fpm_children_make(), line 352: child
31288 (pool default) started
Apr 09 19:24:28.689206 [NOTICE] fpm_children_make(), line 352: child
31289 (pool default) started
Apr 09 19:24:28.690023 [NOTICE] fpm_children_make(), line 352: child
31290 (pool default) started
Apr 09 19:24:28.690055 [NOTICE] fpm_event_loop(), line 107: libevent:
entering main loop
Apr 09 19:35:22.814951 [WARNING] fpm_stdio_child_said(), line 167:
child 31290 (pool default) said into stderr: "sh: -t: command not
found"
Apr 09 19:37:31.266649 [WARNING] fpm_stdio_child_said(), line 167:
child 31287 (pool default) said into stderr: "sh: -t: command not
found"
Apr 09 19:44:06.863229 [WARNING] fpm_stdio_child_said(), line 167:
child 31290 (pool default) said into stderr: "sh: -t: command not
found"
Apr 09 19:59:09.549533 [NOTICE] fpm_got_signal(), line 56: received
SIGTERM
Apr 09 19:59:09.549571 [NOTICE] fpm_pctl(), line 256: switching to
'terminating' state
Apr 09 19:59:09.549603 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 31290 (pool default)
Apr 09 19:59:09.549619 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 31289 (pool default)
Apr 09 19:59:09.549634 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 31288 (pool default)
Apr 09 19:59:09.549646 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 31287 (pool default)
Apr 09 19:59:09.553841 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 31286 (pool default)
Apr 09 19:59:09.553876 [NOTICE] fpm_pctl_kill_all(), line 181: 5
children are still alive
Apr 09 19:59:09.553889 [NOTICE] fpm_got_signal(), line 48: received
SIGCHLD
Apr 09 19:59:09.553923 [WARNING] fpm_children_bury(), line 215: child
31286 (pool default) exited on signal 15 SIGTERM after 2080.867139
seconds from start
Apr 09 19:59:09.553953 [WARNING] fpm_children_bury(), line 215: child
31287 (pool default) exited on signal 15 SIGTERM after 2080.866286
seconds from start
Apr 09 19:59:09.553976 [WARNING] fpm_children_bury(), line 215: child
31290 (pool default) exited on signal 15 SIGTERM after 2080.863963
seconds from start
Apr 09 19:59:09.554631 [NOTICE] fpm_got_signal(), line 48: received
SIGCHLD
Apr 09 19:59:09.554655 [WARNING] fpm_children_bury(), line 215: child
31288 (pool default) exited on signal 15 SIGTERM after 2080.866172
seconds from start
Apr 09 19:59:09.556065 [NOTICE] fpm_got_signal(), line 48: received
SIGCHLD
Apr 09 19:59:09.556090 [WARNING] fpm_children_bury(), line 215: child
31289 (pool default) exited on signal 15 SIGTERM after 2080.866894
seconds from start
Apr 09 19:59:09.556101 [NOTICE] fpm_pctl_exit(), line 81: exiting, bye-
bye!
Apr 09 19:59:10.572571 [NOTICE] fpm_unix_init_main(), line 284:
getrlimit(nofile): max:1024, cur:1024
Apr 09 19:59:10.572799 [NOTICE] fpm_event_init_main(), line 88:
libevent: using epoll
Apr 09 19:59:10.572887 [NOTICE] fpm_init(), line 52: fpm is running,
pid 31809
Apr 09 19:59:10.573801 [NOTICE] fpm_children_make(), line 352: child
31810 (pool default) started
Apr 09 19:59:10.574691 [NOTICE] fpm_children_make(), line 352: child
31811 (pool default) started
Apr 09 19:59:10.575522 [NOTICE] fpm_children_make(), line 352: child
31812 (pool default) started
Apr 09 19:59:10.576252 [NOTICE] fpm_children_make(), line 352: child
31813 (pool default) started
Apr 09 19:59:10.577191 [NOTICE] fpm_children_make(), line 352: child
31814 (pool default) started
Apr 09 19:59:10.577221 [NOTICE] fpm_event_loop(), line 107: libevent:
entering main loop
Apr 11 13:56:46.631069 [NOTICE] fpm_unix_init_main(), line 284:
getrlimit(nofile): max:1024, cur:1024
Apr 11 13:56:46.637229 [NOTICE] fpm_event_init_main(), line 88:
libevent: using epoll
Apr 11 13:56:46.641404 [NOTICE] fpm_init(), line 52: fpm is running,
pid 6215
Apr 11 13:56:46.641755 [NOTICE] fpm_children_make(), line 352: child
6216 (pool default) started
Apr 11 13:56:46.642422 [NOTICE] fpm_children_make(), line 352: child
6217 (pool default) started
Apr 11 13:56:46.642674 [NOTICE] fpm_children_make(), line 352: child
6218 (pool default) started
Apr 11 13:56:46.643322 [NOTICE] fpm_children_make(), line 352: child
6219 (pool default) started
Apr 11 13:56:46.643587 [NOTICE] fpm_children_make(), line 352: child
6220 (pool default) started
Apr 11 13:56:46.643617 [NOTICE] fpm_event_loop(), line 107: libevent:
entering main loop
Apr 12 06:47:16.804647 [NOTICE] fpm_got_signal(), line 48: received
SIGCHLD
Apr 12 06:47:16.804697 [WARNING] fpm_children_bury(), line 215: child
6217 (pool default) exited on signal 4 SIGILL after 60630.162283
seconds from start
Apr 12 06:47:16.805523 [NOTICE] fpm_children_make(), line 352: child
18788 (pool default) started
Apr 12 06:48:15.937609 [NOTICE] fpm_got_signal(), line 48: received
SIGCHLD
Apr 12 06:48:15.937672 [WARNING] fpm_children_bury(), line 215: child
6218 (pool default) exited on signal 4 SIGILL after 60689.295013
seconds from start
Apr 12 06:48:15.937998 [NOTICE] fpm_children_make(), line 352: child
29467 (pool default) started
Apr 12 06:50:50.206681 [NOTICE] fpm_got_signal(), line 48: received
SIGCHLD
Apr 12 06:50:50.206732 [WARNING] fpm_children_bury(), line 215: child
6219 (pool default) exited on signal 4 SIGILL after 60843.563419
seconds from start
Apr 12 06:50:50.208420 [NOTICE] fpm_children_make(), line 352: child
13913 (pool default) started
Apr 12 06:51:02.349724 [NOTICE] fpm_got_signal(), line 56: received
SIGTERM
Apr 12 06:51:02.349763 [NOTICE] fpm_pctl(), line 256: switching to
'terminating' state
Apr 12 06:51:02.349800 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 13913 (pool default)
Apr 12 06:51:02.349815 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 29467 (pool default)
Apr 12 06:51:02.349828 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 18788 (pool default)
Apr 12 06:51:02.351209 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 6220 (pool default)
Apr 12 06:51:02.351246 [NOTICE] fpm_pctl_kill_all(), line 172: sending
signal 15 SIGTERM to child 6216 (pool default)
Apr 12 06:51:02.351256 [NOTICE] fpm_pctl_kill_all(), line 181: 5
children are still alive
Apr 12 06:51:02.351268 [NOTICE] fpm_got_signal(), line 48: received
SIGCHLD
Apr 12 06:51:02.351292 [WARNING] fpm_children_bury(), line 215: child
6220 (pool default) exited on signal 15 SIGTERM after 60855.707722
seconds from start
Apr 12 06:51:02.351322 [WARNING] fpm_children_bury(), line 215: child
18788 (pool default) exited on signal 15 SIGTERM after 225.545810
seconds from start
Apr 12 06:51:02.351369 [WARNING] fpm_children_bury(), line 215: child
29467 (pool default) exited on signal 15 SIGTERM after 166.413393
seconds from start
Apr 12 06:51:02.351391 [WARNING] fpm_children_bury(), line 215: child
13913 (pool default) exited on signal 15 SIGTERM after 12.142983
seconds from start
Apr 12 06:51:02.352981 [NOTICE] fpm_got_signal(), line 48: received
SIGCHLD
Apr 12 06:51:02.352999 [WARNING] fpm_children_bury(), line 215: child
6216 (pool default) exited on signal 15 SIGTERM after 60855.711283
seconds from start
Apr 12 06:51:02.353010 [NOTICE] fpm_pctl_exit(), line 81: exiting, bye-
bye!

After reading some articles around the web I believe it has something
to do with my php-fpm.conf which is bellow:
<?xml version="1.0" ?>
<configuration>
<section name="global_options">
<value name="pid_file">/usr/local/logs/php-fpm.pid</
value>
<value name="error_log">/usr/local/logs/php-fpm.log</
value>
<value name="log_level">notice</value>
<value name="emergency_restart_threshold">10</value>
<value name="emergency_restart_interval">1m</value>
<value name="process_control_timeout">5s</value>
<value name="daemonize">no</value>
</section>
<workers>
<section name="pool">
<value name="name">default</value>
<value name="listen_address">127.0.0.1:9000</
value>
<value name="listen_options">
<value name="backlog">-1</value>
<value name="owner">www-data</value>
<value name="group">www-data</value>
<value name="mode">0666</value>
</value>
<value name="php_defines">
<!-- <value name="sendmail_path">/usr/sbin/
sendmail -t -i</value> -->
<!-- <value name="display_errors">0</
value> -->
</value>
<value name="user">www-data</value>
<value name="group">www-data</value>
<value name="pm">
<value name="style">apache-like</
value>
<value name="max_children">5</value>
<value name="apache_like">
<value name="StartServers">20</
value>
<value
name="MinSpareServers">5</value>
<value
name="MaxSpareServers">35</value>

</value>

</value>
<value name="request_terminate_timeout">0s</
value>
<value name="request_slowlog_timeout">0s</
value>
<value name="slowlog">logs/slow.log</value>
<value name="rlimit_files">65535</value>
<value name="rlimit_core">0</value>
<value name="chroot"></value>
<value name="chdir"></value>
<value name="catch_workers_output">yes</value>
<value name="max_requests">102400</value>
<value name="allowed_clients">127.0.0.1</
value>
<value name="environment">
<value name="HOSTNAME">$HOSTNAME</
value>
<value name="PATH">/usr/local/bin:/usr/
bin:/bin</value>
<value name="TMP">/tmp</value>
<value name="TMPDIR">/tmp</value>
<value name="TEMP">/tmp</value>
<value name="OSTYPE">$OSTYPE</value>
<value name="MACHTYPE">$MACHTYPE</
value>
<value name="MALLOC_CHECK_">2</value>
</value>
</section>
</workers>
</configuration>

I`ve tried changing rlimit_files, pm style, max_children and
max_requests but I get the same error no matter what.

Thanks in avance for any suggestion!


--
To unsubscribe, reply using "remove me" as the subject.
Gordon Pettey
Re: PHP-FPM not starting with segment fault error
April 15, 2010 12:36PM
1. Why is daemonize set to no?
2. Docs clearly state that apache-like is not implemented.


--
To unsubscribe, reply using "remove me" as the subject.
DiliBau
Re: PHP-FPM not starting with segment fault error
April 15, 2010 12:42PM
From php-fpm.conf
Set to 'no' to debug fpm
<value name="daemonize">no</value>
On Apr 15, 7:35 pm, Gordon Pettey <petteyg...@gmail.com> wrote:
> 1. Why is daemonize set to no?
> 2. Docs clearly state that apache-like is not implemented.


--
To unsubscribe, reply using "remove me" as the subject.
DiliBau
Re: PHP-FPM not starting with segment fault error
April 15, 2010 12:48PM
From php-fpm.conf
Set to 'no' to debug fpm
<value name="daemonize">no</value>

On Apr 15, 7:35 pm, Gordon Pettey <petteyg...@gmail.com> wrote:
> 1. Why is daemonize set to no?
> 2. Docs clearly state that apache-like is not implemented.


--
To unsubscribe, reply using "remove me" as the subject.
Jérôme Loyet
Re: PHP-FPM not starting with segment fault error
April 15, 2010 12:48PM
2010/4/15 DiliBau <radu1658@gmail.com>:
> From php-fpm.conf
>                Set to 'no' to debug fpm
>                <value name="daemonize">no</value>
> On Apr 15, 7:35 pm, Gordon Pettey <petteyg...@gmail.com> wrote:
>> 1. Why is daemonize set to no?
>> 2. Docs clearly state that apache-like is not implemented.
>

It's implemented in the dev version (from PHP SVN trunk).
Which documentation are you referencing here ?


--
To unsubscribe, reply using "remove me" as the subject.
Gordon Pettey
Re: PHP-FPM not starting with segment fault error
April 15, 2010 12:48PM
"Debug" generally refers to debugging with gdb, which you don't seem
to be doing. Use static pm and put daemonize back to yes, then post
your log file.


--
To unsubscribe, reply using "remove me" as the subject.
Jérôme Loyet
Re: PHP-FPM not starting with segment fault error
April 15, 2010 12:48PM
2010/4/15 DiliBau <radu1658@gmail.com>:
> Basically when I run "php-fpm start" I get Sement fault and that`s
> about it regarding error messages.
>

which version of FPM are you using (and which version of PHP) ?


--
To unsubscribe, reply using "remove me" as the subject.
Jérôme Loyet
Re: PHP-FPM not starting with segment fault error
April 15, 2010 12:50PM
2010/4/15 Gordon Pettey <petteyg359@gmail.com>:
> "Debug" generally refers to debugging with gdb, which you don't seem
> to be doing. Use static pm and put daemonize back to yes, then post
> your log file.
>

Setting daemonize to no makes FPM to stay in foreground so that you
can see the log in your terminal and stop FPM by CTRL+C. I'm using it
everyday to test FPM. There is nothing to do with gdb.


--
To unsubscribe, reply using "remove me" as the subject.
DiliBau
Re: PHP-FPM not starting with segment fault error
April 15, 2010 12:52PM
php 5.3.2 with fpm 0.6.5-5.3.1

On Apr 15, 7:47 pm, Jérôme Loyet <m...@fatbsd.com> wrote:
> 2010/4/15 DiliBau <radu1...@gmail.com>:
>
> > Basically when I run "php-fpm start" I get Sement fault and that`s
> > about it regarding error messages.
>
> which version of FPM are you using (and which version of PHP) ?


--
To unsubscribe, reply using "remove me" as the subject.
Re: PHP-FPM not starting with segment fault error
April 15, 2010 12:56PM
I thought it was called 'dynamic' now?

On Apr 15, 2010, at 9:46 AM, Jérôme Loyet <ml@fatbsd.com> wrote:

> 2010/4/15 DiliBau <radu1658@gmail.com>:
>> From php-fpm.conf
>> Set to 'no' to debug fpm
>> <value name="daemonize">no</value>
>> On Apr 15, 7:35 pm, Gordon Pettey <petteyg...@gmail.com> wrote:
>>> 1. Why is daemonize set to no?
>>> 2. Docs clearly state that apache-like is not implemented.
>>
>
> It's implemented in the dev version (from PHP SVN trunk).
> Which documentation are you referencing here ?
>
>
> --
> To unsubscribe, reply using "remove me" as the subject.
Jérôme Loyet
Re: PHP-FPM not starting with segment fault error
April 15, 2010 12:56PM
2010/4/15 DiliBau <radu1658@gmail.com>:
> php 5.3.2 with fpm 0.6.5-5.3.1

can you try building the last dev version otherwise I won't be able to help you.

checkout http://php-fpm.org/download/ and see "PHP Core - Experimental
(PHP 5.3.x)"

it should work with php 5.3.1 but it's better if you use php 5.3.2.

>
> On Apr 15, 7:47 pm, Jérôme Loyet <m...@fatbsd.com> wrote:
>> 2010/4/15 DiliBau <radu1...@gmail.com>:
>>
>> > Basically when I run "php-fpm start" I get Sement fault and that`s
>> > about it regarding error messages.
>>
>> which version of FPM are you using (and which version of PHP) ?
>
>
> --
> To unsubscribe, reply using "remove me" as the subject.
>
Jérôme Loyet
Re: PHP-FPM not starting with segment fault error
April 15, 2010 12:58PM
2010/4/15 Michael Shadle <mike503@gmail.com>:
> I thought it was called 'dynamic' now?

yes it is

but they are talking about an old version ...

>
> On Apr 15, 2010, at 9:46 AM, Jérôme Loyet <ml@fatbsd.com> wrote:
>
>> 2010/4/15 DiliBau <radu1658@gmail.com>:
>>>
>>> From php-fpm.conf
>>>               Set to 'no' to debug fpm
>>>               <value name="daemonize">no</value>
>>> On Apr 15, 7:35 pm, Gordon Pettey <petteyg...@gmail.com> wrote:
>>>>
>>>> 1. Why is daemonize set to no?
>>>> 2. Docs clearly state that apache-like is not implemented.
>>>
>>
>> It's implemented in the dev version (from PHP SVN trunk).
>> Which documentation are you referencing here ?
>>
>>
>> --
>> To unsubscribe, reply using "remove me" as the subject.
>
DiliBau
Re: PHP-FPM not starting with segment fault error
April 15, 2010 02:02PM
I`ve compiled the latest fpm from svn with php 5.3.2 and i still get
the segment fault error, any other ideas?

On Apr 15, 7:55 pm, Jérôme Loyet <m...@fatbsd.com> wrote:
> 2010/4/15 Michael Shadle <mike...@gmail.com>:
>
> > I thought it was called 'dynamic' now?
>
> yes it is
>
> but they are talking about an old version ...
>
>
>
> > On Apr 15, 2010, at 9:46 AM, Jérôme Loyet <m...@fatbsd.com> wrote:
>
> >> 2010/4/15 DiliBau <radu1...@gmail.com>:
>
> >>> From php-fpm.conf
> >>>               Set to 'no' to debug fpm
> >>>               <value name="daemonize">no</value>
> >>> On Apr 15, 7:35 pm, Gordon Pettey <petteyg...@gmail.com> wrote:
>
> >>>> 1. Why is daemonize set to no?
> >>>> 2. Docs clearly state that apache-like is not implemented.
>
> >> It's implemented in the dev version (from PHP SVN trunk).
> >> Which documentation are you referencing here ?
>
> >> --
> >> To unsubscribe, reply using "remove me" as the subject.
>
>
DiliBau
Re: PHP-FPM not starting with segment fault error
April 15, 2010 02:04PM
On Apr 15, 7:55 pm, Jérôme Loyet <m...@fatbsd.com> wrote:
> 2010/4/15 DiliBau <radu1...@gmail.com>:
>
> > php 5.3.2 with fpm 0.6.5-5.3.1
>
> can you try building the last dev version otherwise I won't be able to help you.
>
> checkouthttp://php-fpm.org/download/and see "PHP Core - Experimental
> (PHP 5.3.x)"
>
> it should work with php 5.3.1 but it's better if you use php 5.3.2.
>
>
>
> > On Apr 15, 7:47 pm, Jérôme Loyet <m...@fatbsd.com> wrote:
> >> 2010/4/15 DiliBau <radu1...@gmail.com>:
>
> >> > Basically when I run "php-fpm start" I get Sement fault and that`s
> >> > about it regarding error messages.
>
> >> which version of FPM are you using (and which version of PHP) ?
>
> > --
> > To unsubscribe, reply using "remove me" as the subject.
>
>

i did what you said and i get the same Segment fault error, should i
try with php 5.3.1 instead of 5.3.2 ?
Jérôme Loyet
Re: PHP-FPM not starting with segment fault error
April 15, 2010 08:06PM
2010/4/15 DiliBau <radu1658@gmail.com>:
> On Apr 15, 7:55 pm, Jérôme Loyet <m...@fatbsd.com> wrote:
>> 2010/4/15 DiliBau <radu1...@gmail.com>:
>>
>> > php 5.3.2 with fpm 0.6.5-5.3.1
>>
>> can you try building the last dev version otherwise I won't be able to help you.
>>
>> checkouthttp://php-fpm.org/download/and see "PHP Core - Experimental
>> (PHP 5.3.x)"
>>
>> it should work with php 5.3.1 but it's better if you use php 5.3.2.
>>
>>
>>
>> > On Apr 15, 7:47 pm, Jérôme Loyet <m...@fatbsd.com> wrote:
>> >> 2010/4/15 DiliBau <radu1...@gmail.com>:
>>
>> >> > Basically when I run "php-fpm start" I get Sement fault and that`s
>> >> > about it regarding error messages.
>>
>> >> which version of FPM are you using (and which version of PHP) ?
>>
>> > --
>> > To unsubscribe, reply using "remove me" as the subject.
>>
>>
>
> i did what you said and i get the same Segment fault error, should i
> try with php 5.3.1 instead of 5.3.2 ?

nope it won't be necessary.

how did you compile php (configure options) to add FPM support ?
did you changed you configuration file ?
is the error log the same as before ?

++ Jerome
DiliBau
Re: PHP-FPM not starting with segment fault error
April 16, 2010 05:22PM
I`ve downloaded php-5.3.2 from php.net and I`ve added php-fpm from
svn, then compiled it with
../configure --enable-fastcgi --with-mcrypt --with-zlib --enable-
mbstring --disable-pdo --with-pgsql --with-curl=/usr/include/curl --
disable-debug --enable-pic --disable-rpath --enable-inline-
optimization --with-bz2 --with-xml --enable-sockets --enable-sysvsem --
enable-sysvshm --enable-pcntl --enable-mbregex --with-mhash --enable-
xslt --enable-memcache --enable-zip --with-pcre-regex --with-mysql=/
usr/include/mysql --enable-mysql --with-gd=/usr/lib --with-freetype-
dir=/usr/lib --with-png-dir=/usr/include/libpng --with-jpeg-dir=/usr/
include --with-libevent=shared,/usr/local/lib/libevent.so --with-xpm-
dir=/usr/include/X11 --enable-gd-native-ttf --enable-fpm --with-fpm-
user=www-data --with-fpm-group=www-data

On Apr 16, 3:04 am, Jérôme Loyet <m...@fatbsd.com> wrote:
> 2010/4/15 DiliBau <radu1...@gmail.com>:
>
>
>
> > On Apr 15, 7:55 pm, Jérôme Loyet <m...@fatbsd.com> wrote:
> >> 2010/4/15 DiliBau <radu1...@gmail.com>:
>
> >> > php 5.3.2 with fpm 0.6.5-5.3.1
>
> >> can you try building the last dev version otherwise I won't be able to help you.
>
> >> checkouthttp://php-fpm.org/download/andsee "PHP Core - Experimental
> >> (PHP 5.3.x)"
>
> >> it should work with php 5.3.1 but it's better if you use php 5.3.2.
>
> >> > On Apr 15, 7:47 pm, Jérôme Loyet <m...@fatbsd.com> wrote:
> >> >> 2010/4/15 DiliBau <radu1...@gmail.com>:
>
> >> >> > Basically when I run "php-fpm start" I get Sement fault and that`s
> >> >> > about it regarding error messages.
>
> >> >> which version of FPM are you using (and which version of PHP) ?
>
> >> > --
> >> > To unsubscribe, reply using "remove me" as the subject.
>
> > i did what you said and i get the same Segment fault error, should i
> > try with php 5.3.1 instead of 5.3.2 ?
>
> nope it won't be necessary.
>
> how did you compile php (configure options) to add FPM support ?
> did you changed you configuration file ?
> is the error log the same as before ?
>
> ++ Jerome
Jérôme Loyet
Re: PHP-FPM not starting with segment fault error
April 23, 2010 02:48PM
2010/4/16 DiliBau <radu1658@gmail.com>:
> I`ve downloaded php-5.3.2 from php.net and I`ve added php-fpm from
> svn, then compiled it with
> ./configure --enable-fastcgi --with-mcrypt --with-zlib --enable-
> mbstring --disable-pdo --with-pgsql --with-curl=/usr/include/curl --
> disable-debug --enable-pic --disable-rpath --enable-inline-
> optimization --with-bz2 --with-xml --enable-sockets --enable-sysvsem --
> enable-sysvshm --enable-pcntl --enable-mbregex --with-mhash --enable-
> xslt --enable-memcache --enable-zip --with-pcre-regex --with-mysql=/
> usr/include/mysql --enable-mysql --with-gd=/usr/lib --with-freetype-
> dir=/usr/lib --with-png-dir=/usr/include/libpng --with-jpeg-dir=/usr/
> include --with-libevent=shared,/usr/local/lib/libevent.so --with-xpm-
> dir=/usr/include/X11 --enable-gd-native-ttf --enable-fpm --with-fpm-
> user=www-data --with-fpm-group=www-data

do you still have segfaults ?

Can you provide a stacktrace somehow ?

>
> On Apr 16, 3:04 am, Jérôme Loyet <m...@fatbsd.com> wrote:
>> 2010/4/15 DiliBau <radu1...@gmail.com>:
>>
>>
>>
>> > On Apr 15, 7:55 pm, Jérôme Loyet <m...@fatbsd.com> wrote:
>> >> 2010/4/15 DiliBau <radu1...@gmail.com>:
>>
>> >> > php 5.3.2 with fpm 0.6.5-5.3.1
>>
>> >> can you try building the last dev version otherwise I won't be able to help you.
>>
>> >> checkouthttp://php-fpm.org/download/andsee "PHP Core - Experimental
>> >> (PHP 5.3.x)"
>>
>> >> it should work with php 5.3.1 but it's better if you use php 5.3.2.
>>
>> >> > On Apr 15, 7:47 pm, Jérôme Loyet <m...@fatbsd.com> wrote:
>> >> >> 2010/4/15 DiliBau <radu1...@gmail.com>:
>>
>> >> >> > Basically when I run "php-fpm start" I get Sement fault and that`s
>> >> >> > about it regarding error messages.
>>
>> >> >> which version of FPM are you using (and which version of PHP) ?
>>
>> >> > --
>> >> > To unsubscribe, reply using "remove me" as the subject.
>>
>> > i did what you said and i get the same Segment fault error, should i
>> > try with php 5.3.1 instead of 5.3.2 ?
>>
>> nope it won't be necessary.
>>
>> how did you compile php (configure options) to add FPM support ?
>> did you changed you configuration file ?
>> is the error log the same as before ?
>>
>> ++ Jerome
>
Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 209
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready