| Author |
|
greghuston
Newbie
Joined: 02 September 2015
Online Status: Offline
Posts: 4
|
| Posted: 02 September 2015 at 11:00pm | IP Logged
|
|
|
Hi,
Working on getting afterlogic setup on a new server of mine... I'm having a problem with the log files. Whenever I login to the admin area and go System > Logging > View Log, I always get this error...
Log file can't be read
I'm looking at my permissions and owners and as follows:
./data nginx:nginx 755
Which I believe is the correct setting as I followed the installation instructions carefully, and ran the installation wizard. At this point I'm kind of wondering what's going on? Any pointers?
Greg
|
| Back to Top |
|
| |
Igor
AfterLogic Support
Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6087
|
| Posted: 03 September 2015 at 3:46am | IP Logged
|
|
|
Apparently, those permissions are not sufficient in your case of webserver configuration. Try setting those to 777 for testing purposes and see if it works for you.
--
Regards,
Igor, AfterLogic Support
|
| Back to Top |
|
| |
greghuston
Newbie
Joined: 02 September 2015
Online Status: Offline
Posts: 4
|
| Posted: 03 September 2015 at 9:56pm | IP Logged
|
|
|
Hi,
I set those to 777 and 666 as listed in the installation...
If the permission settings described above don't work for you, you may try to repeat "Assigning owners/permissions" step, but use 777 instead of 755 and 666 instead of 644 (although this is less secure).
And yet I still get the same error? Any ideas why this might be so? There are no log files in that folder either, so I'm not sure if I have to manually create them first or what?
|
| Back to Top |
|
| |
Igor
AfterLogic Support
Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6087
|
| Posted: 04 September 2015 at 3:51am | IP Logged
|
|
|
Setting permissions to 777 is the only suggestion we have. Make sure you assign the permissions recursively, for example:
If the permissions allow for writing into the directory and its subdirectories, log files should be created just fine.
--
Regards,
Igor, AfterLogic Support
|
| Back to Top |
|
| |
greghuston
Newbie
Joined: 02 September 2015
Online Status: Offline
Posts: 4
|
| Posted: 04 September 2015 at 9:35pm | IP Logged
|
|
|
Hi,
Confirmed that directory recursively is 777. Yet still no log files. Two things I'm thinking...
1) Can you tell me the NAME of the actual files and I will manually create them and see if it can write to them after that?
2) I'm a running Nginx not apache. Is that an issue?
Help me out here I've tried your product and want to buy it if I can only get it to work.
Cheers
Greg
|
| Back to Top |
|
| |
Igor
AfterLogic Support
Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6087
|
| Posted: 07 September 2015 at 4:09am | IP Logged
|
|
|
Log files are stored under data/logs/ directory and have the following filename pattern: log-YYYY-MM-DD.txt - for example, log-2015-09-07.txt
And no, using nginx shouldn't be a problem, it's the webserver solution we use ourselves in our mailserver bundles. The suggestion we have is to try changing directory ownership rather than permissions. Run the following command:
It will show nginx processes currently running, and user/group those run under. Using that information, change data directory ownership with a command like this:
Code:
| chown user:group -R /var/www/webmail/data/ |
|
|
- with properly supplied user, group, and path to the data directory.
Hope this helps!
--
Regards,
Igor, AfterLogic Support
|
| Back to Top |
|
| |
MailBee.NET Objects 
MailBee.NET Queue 
MailBee Objects 
WebMail Pro PHP 
AfterLogic Aurora 
MailSuite Pro for Linux 
Unified Messaging Solution 
Search
Register
Login
Topic: Afterlogic Log File Problem
Privacy policy |
Refund policy