logfile entry

HaDe

New Member
#1
Hello
since 1.4.37 i found a lot of "path is not accessible" in servers error.log
is that a bug? site is working fine here.
 

HaDe

New Member
#3
2018-09-07 16:55:05.187177 [ERROR] path is not accessible: /var/www/((*))/wp/wp-json/
2018-09-07 16:55:05.242381 [ERROR] path is not accessible: /var/www/((*))/wp/wp-json/
2018-09-07 16:55:05.300429 [ERROR] path is not accessible: /var/www/((*))/wp/wp-json/
2018-09-07 16:55:05.373051 [ERROR] path is not accessible: /var/www/((*))/wp/wp-json/
2018-09-07 16:55:05.766942 [ERROR] path is not accessible: /var/www/((*))/web/sortiment/
2018-09-07 16:55:06.134072 [ERROR] path is not accessible: /var/www/((*))/web/wp/wp-json/
2018-09-07 16:55:06.198286 [ERROR] path is not accessible: /var/www/((*))/web/wp/wp-json/
2018-09-07 16:55:06.254279 [ERROR] path is not accessible: /var/www/((*))/web/wp/wp-json/
2018-09-07 16:55:06.309250 [ERROR] path is not accessible: /var/www/((*))/web/wp/wp-json/
2018-09-07 16:55:06.376066 [ERROR] path is not accessible: /var/www/((*))/web/wp/wp-json/
2018-09-07 16:55:07.195770 [ERROR] path is not accessible: /var/www/((*))/web/sortiment/
2018-09-07 16:55:07.561021 [ERROR] path is not accessible: /var/www/((*))/web/wp/wp-json/
2018-09-07 16:55:07.771195 [ERROR] path is not accessible: /var/www((*))/web/wp/wp-json/
2018-09-07 16:55:07.827655 [ERROR] path is not accessible: /var/www/((*))/web/wp/wp-json/

the config is as follow: error.log is separated for every vhost.
the url is rewritten (shopware) and works

but

every site call leaves a new entry in servers error.log , but not in the vhost error.log

any ideas ?
 

Pong

Administrator
#4
which user and group do you run OLS? nobody:nobody?

/var/www/ may give "Apache:Apache" user access by default, may not for "nobody:nobody", you should give OLS web server access to it.
 

HaDe

New Member
#5
user nobody can read $DOC_ROOT, no changes.
sub path does not exists because it is rewritten

any changes in last version? before i dont recognized.
 

Pong

Administrator
#6
I am not aware of any changes particular for you case. Not sure what do you mean "sub path rewritten"? Not sure how you use /var/www/ for? Is that home for all your virtuahost? You can just change permission to be accessible. Since I don't know your server configuration, hard to tell. For me, if I make /usr/local/lsws as server root and /usr/local/lsws/$VH1 , /usr/local/lsws/$VH2, ... I won't see your error. If you define something to /var/www/, then make sure the permission right.
 

HaDe

New Member
#7
ok... here are some info about the server config.
I'm using ISPConfig for the server configuation. but nginx dont listen to 80 or 443.
vhosts are in /var/www/etc....

lsws has vhosts in the same direcoty. lsphp is running as same user as nginx (web1 etc) and listen to 80 / 443
everything works fine (lsws sometimes restart with signal 6 oder 11 randomly, email is out to bug@...) but otherwise everythings is cool.

shopware has rewrite rules, which does all routing. (to one file shopware.php) configured in the web interface.
Site is working . no 404 etc. also access log shows 200 .
but I found the logs in servers error.log. they shouldn be there, because it works fine.

maybe you changes something in your rewrite engine ( i regognized that since last version lsws tries to read htaccess - before it ignored because of GPLv3 license)
 

Pong

Administrator
#8
signal 6 seems some bug, if you forward it to bug@, our developer will look at it further.

Yes, new version of OLS will read your .htaccess file ( but only rewrite rules, everything else will not be recognized by OLS).

If you still worry about the 2018-09-07 16:55:07.827655 [ERROR] path is not accessible: /var/www/((*))/web/wp/wp-json/, please log a ticket with us by providing tmp root ssh password to your server, we can take a look.
 
Top