I had a similar problem today.  My workers file definitely existed but I kept 
getting 'no such file' errors.
It turned out I had the JkWorkersFile directive defined inside a <VirtualHost> 
container.  Moving it outside solved the problem.

Patrick


On Wed, 29 Oct 2003 09:01 pm, Alexander Prohorenko wrote:
> Hello,
>
> I can't get it run guys.
>
> That's what I have there:
>
> [Wed Oct 29 02:36:35 2003] [error] Error while opening the workers, jk will
> not work
>
> [Wed Oct 29 02:36:36 2003] [info] mod_unique_id: using ip addr
> 192.168.185.115 [Wed Oct 29 02:36:37 2003] [info] (2)No such file or
> directory: make_sock: for port 443, setsockopt: (SO_ACCEPTFILTER) [Wed Oct
> 29 02:36:37 2003] [info] (2)No such file or directory: make_sock: for port
> 80, setsockopt: (SO_ACCEPTFILTER) [Wed Oct 29 02:36:37 2003] [error] (2)No
> such file or directory: Error while opening the workers, jk will not work
>
> [Wed Oct 29 02:36:37 2003] [info] mod_unique_id: using ip addr
> 192.168.185.115 [Wed Oct 29 02:36:38 2003] [notice] Apache/1.3.28 (Unix)
> PHP/4.1.2 mod_ssl/2.8.15 OpenSSL/0.9.7a configured -- resuming normal
> operations [Wed Oct 29 02:36:38 2003] [info] Server built: Aug  4 2003
> 00:42:33 [Wed Oct 29 02:36:38 2003] [notice] Accept mutex: flock (Default:
> flock)
>
>
> However, everything exists.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to