|
Jason
|
November 2, 2015 at 1:21 pm
Hi,
I’m having what appears to be a permissions problem when enabling EE4 logging. After WP_DEBUG is turned on I get this message:
An error has occurred:
Event Espresso logging could not be setup because: “/usr2/www/html/xyz.com/wp-content/uploads/espresso/” could not be created.Please ensure that the server and/or PHP configuration allows the current process to access the following file: “/usr2/www/html/xyz.com/wp-content/uploads/espresso/”.
EE_Log – verify_filesystem – 118
Except that directory already exists and is writable by the web server user:
$ ls -ld /usr2/www/html/xyz.com/wp-content/uploads/espresso/
drwxrwxr-x 3 xyz.com apache 4096 Nov 2 19:19 /usr2/www/html/xyz.com/wp-content/uploads/espresso/
Even if I set it to world writable and chown it to the apache user it still gives the same message.
Any suggestions?
WordPress Version: 4.3.1
PHP Version: 5.3.29
MySQL Version: 5.5.45
Event Espresso Version: 4.8.18.p
Thanks,
Jason
|
|
Jason
|
November 3, 2015 at 3:44 pm
It looks like this is because my server is using FS_METHOD of ssh2.
The call to EEH_File::_get_wp_filesystem(); fails with SSH2 hostname, username & pw is required. The server is set to use FTP_PUBKEY / FTP_PRIKEY and those are defined and works fine for regular updates and installs but not EE it seems.
If I change to
define('FS_METHOD', 'direct');
It works ok though that breaks updates & installs of everything else because of the filesystem permissions.
Anything that could be done to get it to work with ssh2?
thanks,
Jason
|
|
Lorenzo Orlando Caum
|
November 5, 2015 at 9:21 am
Hi there Jason,
I’m not familiar with SSH2 so I would like to check with our development team.
Are the SSH2 credentials stored in the wp-config.php file or are they being entered on demand?
Thanks
—
Lorenzo
|
|
Jason
|
November 5, 2015 at 9:29 am
Hi Lorenzo,
Yes, the keys used are configured in the wp-config.php, like this:
define('FTP_PUBKEY','/home/wp-user/wp_rsa.pub');
define('FTP_PRIKEY','/home/wp-user/wp_rsa');
define('FTP_USER','wp-user');
define('FTP_PASS','');
define('FTP_HOST','127.0.0.1:22');
As describe in detail here: https://www.digitalocean.com/community/tutorials/how-to-configure-secure-updates-and-installations-in-wordpress-on-ubuntu
So you don’t have to enter anything on-demand.
Thanks,
Jason
|
|
Lorenzo Orlando Caum
|
November 5, 2015 at 10:11 am
Thanks Jason! I’ve created a report for our development team to review and I’ll update your support post as soon as we have more information available.
—
Lorenzo
|
|
Michael Nelson
|
November 6, 2015 at 5:29 pm
Hey Jason, we found a bug in how we were using WordPress’ filesystem code. We are currently testing our fix. You can it a test too by downloading the bugfix copy located on our github repo located here: https://github.com/eventespresso/event-espresso-core/archive/BUG-9038-cannot-enable-logging-over-ssh.zip
But regardless we will be testing that version of the code and putting a fix in our master version asap
|
|
Jason
|
November 7, 2015 at 1:29 pm
Great, thank you. That bugfix copy does fix the issue for me (although it now says my license is expired when I run it?)
|
|
Lorenzo Orlando Caum
|
November 8, 2015 at 10:26 am
Hi Jason,
Thanks for letting us know. I’ve released your support license key and we’ll update this support post once this has been released in the next maintenance release.
At that time, you can remove the 9038 branch and then upload and install the latest release.
Thanks
—
Lorenzo
|
|
Josh
|
November 12, 2015 at 12:05 pm
Update: The fix was included in the latest update of Event Espresso 4.
|
