Search found 56 matches
- Sun Oct 25, 2015 11:26 am
- Forum: General
- Topic: CLOSED: ProFTPD and Monit
- Replies: 3
- Views: 6550
Re: ProFTPD and Monit
Done!
- Sun Oct 25, 2015 10:54 am
- Forum: General
- Topic: CLOSED: ProFTPD and Monit
- Replies: 3
- Views: 6550
CLOSED: ProFTPD and Monit
Looking at my logs, I noticed that the ProFTPD service was being restarted regularly. It appears that monit is doing the restarting, because it is looking for the proftpd.pid file in /var/run/, whilst the file actually resides in /var/run/proftpd. I've updated the monit conf file for proftpd (proftp...
- Mon Sep 07, 2015 2:51 am
- Forum: Backups
- Topic: Crashplan on HDA Set Up
- Replies: 2
- Views: 8466
Re: Crashplan on HDA Set Up
You can change the location of the Crashplan backups from the Crashplan app on the HDA. You need to open the Crashplan desktop application on your HDA, but the method for doing this depends on whether you are running your HDA headless or not. There are some instructions on the wiki here (the ones fo...
- Sun Jul 12, 2015 5:05 am
- Forum: Backups
- Topic: RESOLVED: Crashplan and inotify watches
- Replies: 5
- Views: 10104
Re: Crashplan and inotify watches
Do you have all the OS updates applied? Did you install ntpd or was it installed from the Network Time applicaiton. I think that I have found the problem. I had the Network Time application installed, but it restarted at the end of January following an update and appears to have been running withou...
- Sat Jul 11, 2015 1:22 am
- Forum: Backups
- Topic: RESOLVED: Crashplan and inotify watches
- Replies: 5
- Views: 10104
Re: Crashplan and inotify watches
So will increasing it more help? I am not a big fan of CrashPlan and it often causes problems with Greyhole. Wonder if it's related to Greyhole Inodes issue. It has got rid of the error messages, and it appears to be a known problem, and it is the same as the Greyhole issue, and the same solution s...
- Fri Jul 10, 2015 2:47 pm
- Forum: Backups
- Topic: RESOLVED: Crashplan and inotify watches
- Replies: 5
- Views: 10104
RESOLVED: Crashplan and inotify watches
I was reviewing my logs when I spotted the ntpd service being started every minute or two. Digging into this further, I discovered that restarting ntpd manually ( sudo systemctl restart ntpd.service ) resulted in a " Error: Not enough space on device " message. This got me worried, but che...
- Thu Sep 18, 2014 2:31 pm
- Forum: Suggestions
- Topic: Amahi Anywhere Security
- Replies: 3
- Views: 8116
Re: Amahi Anywhere Security
You can control what shares do not show in the mobile apps by making them invisible (i.e. unclick "visible") in your HDA Setup > Shares area for that share. That is useful to know. I thought that it related to the visibility of shares on the network. Perhaps there needs to be an explanati...
- Thu Sep 18, 2014 7:57 am
- Forum: Suggestions
- Topic: Amahi Anywhere Security
- Replies: 3
- Views: 8116
Amahi Anywhere Security
It is great to see the Amahi Anywhere app for Android working. I have had a quick play, and it works very well. My main concern is security. The app gives access to all shares on the HDA, including those belonging to individual users that would otherwise not be accessible to other users. This seems ...
- Thu Mar 27, 2014 7:53 am
- Forum: Applications
- Topic: Nagios username
- Replies: 1
- Views: 1281
Nagios username
There seems to be a problem with the setup of Nagios in Amahi 7.1. The installer creates a user called admin with the password admin , but this user is not configured within /etc/nagios/cgi.cfg to allow access to Nagios resources, so you get a message saying you don't have rights to view anything ev...
- Mon Mar 03, 2014 3:13 pm
- Forum: Installation
- Topic: SOLVED! - Amahi 7 - Am I having a Fedora problem?
- Replies: 23
- Views: 9535
Re: SOLVED! - Amahi 7 - Am I having a Fedora problem?
It looks like I have been caught by the same issue. The network devices were eth0 and eth1 during the install (from the express CD), but called en0 and eth1 once the HDA is running. The hda does not set its own ip address - there are no IPv4 network addresses for any interface unless I get the route...