cannot delete input or feed - keeps reappearing

Submitted by a234525 on Fri, 18/03/2016 - 20:09

Local emonhub and emoncms on a pi which has been working fine for a few weeks.

I have been experimenting with redis and adding some json uploads from another system. This has meant adding and deleting feeds several times.

I have 3 inputs that I cannot delete. They say "ERROR" under process list on the input screen. When I try and delete them they instantly reappear on the gui.

If I click the spanner icon to go into the process list setup screen, the feeds within the process say "feedid 136 does not exists or was deleted". When I try and delete the processes and press "Save" then a popup appears saying "could not save process list, undefined"

All my main feeds have also stopped updating.

Any ideas how to delete these extra feeds?

Thanks.

Re: cannot delete input or feed - keeps reappearing

Submitted by a234525 on Sun, 20/03/2016 - 08:54.

Anyone?

Re: cannot delete input or feed - keeps reappearing

Submitted by Paul Reed on Sun, 20/03/2016 - 10:12.

Can you try flushing Redis;

redis-cli flushall

Paul

Re: cannot delete input or feed - keeps reappearing

Submitted by a234525 on Sun, 20/03/2016 - 23:54.

Thank you for replying Paul. I get the following message.

pi@emoncms:~ $ redis-cli flushall
(error) MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for details about the error.
pi@emoncms:~ $

thanks!

Re: cannot delete input or feed - keeps reappearing

Submitted by a234525 on Mon, 21/03/2016 - 23:51.

I found the redis log which had entries like this

[544] 21 Mar 23:20:08.057 * 1 changes in 900 seconds. Saving...
[544] 21 Mar 23:20:08.058 # Can't save in background: fork: Cannot allocate memory

After googling for that I set the following switch in sysctl.conf


vm.overcommit_memory=1

Now the feeds seem to be working again. The redis log now says

[543] 21 Mar 23:25:20.640 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
[543] 21 Mar 23:25:20.664 # Redis can't set maximum open files to 10032 because of OS error: Operation not permitted.
[543] 21 Mar 23:25:20.664 # Current maximum open files is 1024. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
[543] 21 Mar 23:25:20.678 # Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with 'noeviction' policy now.
                _._
           _.-``__ ''-._
      _.-``    `.  `_.  ''-._           Redis 2.8.17 (00000000/0) 32 bit
  .-`` .-```.  ```\/    _.,_ ''-._
 (    '      ,       .-`  | `,    )     Running in stand alone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
 |    `-._   `._    /     _.-'    |     PID: 543
  `-._    `-._  `-./  _.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |           http://redis.io
  `-._    `-._`-.__.-'_.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |
  `-._    `-._`-.__.-'_.-'    _.-'
      `-._    `-.__.-'    _.-'
          `-._        _.-'
              `-.__.-'

[543] 21 Mar 23:25:20.739 # Server started, Redis version 2.8.17
[543] 21 Mar 23:28:13.121 * DB loaded from disk: 172.370 seconds
[543] 21 Mar 23:28:13.121 * The server is now ready to accept connections on port 6379
[543] 21 Mar 23:30:21.008 * 10 changes in 300 seconds. Saving...
[543] 21 Mar 23:30:21.049 * Background saving started by pid 1264
[1264] 21 Mar 23:31:33.399 * DB saved on disk
[1264] 21 Mar 23:31:33.481 * RDB: 4 MB of memory used by copy-on-write
[543] 21 Mar 23:31:33.640 * Background saving terminated with success
[543] 21 Mar 23:36:34.002 * 10 changes in 300 seconds. Saving...
[543] 21 Mar 23:36:34.046 * Background saving started by pid 1266
[1266] 21 Mar 23:37:44.773 * DB saved on disk
[1266] 21 Mar 23:37:44.799 * RDB: 4 MB of memory used by copy-on-write
[543] 21 Mar 23:37:44.883 * Background saving terminated with success
[543] 21 Mar 23:42:45.094 * 10 changes in 300 seconds. Saving...
[543] 21 Mar 23:42:45.146 * Background saving started by pid 1332
[1332] 21 Mar 23:43:58.111 * DB saved on disk
[1332] 21 Mar 23:43:58.138 * RDB: 4 MB of memory used by copy-on-write
[543] 21 Mar 23:43:58.219 * Background saving terminated with success

I am worried that there is still a problem. Should I have set that overcommit setting?

thanks,

Archived Forum