Community
OpenEnergyMonitor

Community

Post Processor Menu Item Missing

emonpi
Tags: #<Tag:0x00007f8816f9b9d8>
(Neil Hastings) #1

Hello,

I upgraded to v9.9.9 a couple of days ago and the Post Processor menu item seems to have vanished. I read this post [Post Processor Disappeared]. The solution recommended in that post has not worked for me.

This is what I did:

I’m not certain that the missing post processor is linked to the recent upgrade as I didn’t notice the problem immediately.

Server Information
Services
emonhub Active Running
emoncms_mqtt Active Running
feedwriter Active Running - sleep 60s
service-runner Active Running
emonPiLCD Active Running
redis-server Active Running
mosquitto Active Running
Emoncms Version low-write 9.9.9
Modules Administration : App v1.2.1 : Backup v1.1.6 : EmonHub Config v1.1.0 : Dashboard v1.3.3 : Device v2.0.0 : EventProcesses : Feed : Graph v1.2.3 : Input : Postprocess v2.0.0 : CoreProcess : remoteaccess : Schedule : Network Setup v1.0.0 : sync : Time : User : Visualisation : WiFi v1.3.1
Git URL: https://github.com/emoncms/emoncms.git : Branch: * stable : Describe: 9.9.8-61-g74f8acaf
Server OS Linux 4.14.71-v7+
Host emonpi : emonpi : (192.168.1.11)
Date 2019-05-15 09:25:13 EDT
Uptime 09:25:13 up 23:46, 1 user, load average: 0.57, 0.34, 0.28
HTTP Server Apache/2.4.25 (Raspbian) HTTP/1.1 CGI/1.1 80
MySQL Version 5.5.5-10.1.23-MariaDB-9+deb9u1
Host 127.0.0.1 (127.0.0.1)
Date 2019-05-15 09:25:13 (UTC -04:00‌​)
Stats Uptime: 85597 Threads: 4 Questions: 320815 Slow queries: 0 Opens: 50 Flush tables: 1 Open tables: 44 Queries per second avg: 3.747
Redis Version 3.2.6
Host localhost:6379 (127.0.0.1)
Size
Uptime 0 days
MQTT Server Version Mosquitto 1.4.10
Host localhost:1883 (127.0.0.1)
Pi Model Raspberry Pi 3 Model B+ Rev 1.3 - 1 GB (Sony UK)
SoC Broadcom BCM2835
Serial num. 5ABE4EF9
Temperature CPU: 47.77°C - GPU: 47.2’C
Release emonSD-30Oct18
Memory RAM Used: 25.14% Total: 976.74 MB Used: 245.56 MB Free: 731.18 MB
Swap Used: 0.00% Total: 100 MB Used: 0 B Free: 100 MB
Disk Mount Stats
/ Used: 41.92% Total: 3.81 GB Used: 1.6 GB Free: 2.04 GB
/var/log Used: 3.12% Total: 50 MB Used: 1.56 MB Free: 48.44 MB
/boot Used: 51.69% Total: 42.52 MB Used: 21.98 MB Free: 20.54 MB
/home/pi/data Used: 1.53% Total: 10.32 GB Used: 161.21 MB Free: 9.63 GB
/mnt/usbdrive Used: 0.24% Total: 28.97 GB Used: 70.34 MB Free: 27.4 GB
PHP Version 7.0.30-0+deb9u1 (Zend Version 3.0.0)
Modules apache2handler : calendar v7.0.30-0+deb9u1 : Core v7.0.30-0+deb9u1 : ctype v7.0.30-0+deb9u1 : curl v7.0.30-0+deb9u1 : date v7.0.30-0+deb9u1 : dom v20031129 : exif v7.0.30-0+deb9u1 : fileinfo v1.0.5 : filter v7.0.30-0+deb9u1 : ftp v7.0.30-0+deb9u1 : gd v7.0.30-0+deb9u1 : gettext v7.0.30-0+deb9u1 : hash v1.0 : iconv v7.0.30-0+deb9u1 : igbinary v2.0.1 : json v1.4.0 : libxml v7.0.30-0+deb9u1 : mbstring v7.0.30-0+deb9u1 : mcrypt v7.0.30-0+deb9u1 : mosquitto v0.4.0 : mysqli v7.0.30-0+deb9u1 : mysqlnd vmysqlnd 5.0.12-dev - 20150407 - $Id: b5c5906d452ec590732a93b051f3827e02749b83 $ : openssl v7.0.30-0+deb9u1 : pcre v7.0.30-0+deb9u1 : PDO v7.0.30-0+deb9u1 : pdo_mysql v7.0.30-0+deb9u1 : Phar v2.0.2 : posix v7.0.30-0+deb9u1 : readline v7.0.30-0+deb9u1 : redis v4.1.1 : Reflection v7.0.30-0+deb9u1 : session v7.0.30-0+deb9u1 : shmop v7.0.30-0+deb9u1 : SimpleXML v7.0.30-0+deb9u1 : sockets v7.0.30-0+deb9u1 : SPL v7.0.30-0+deb9u1 : standard v7.0.30-0+deb9u1 : sysvmsg v7.0.30-0+deb9u1 : sysvsem v7.0.30-0+deb9u1 : sysvshm v7.0.30-0+deb9u1 : tokenizer v7.0.30-0+deb9u1 : wddx v7.0.30-0+deb9u1 : xml v7.0.30-0+deb9u1 : xmlreader v7.0.30-0+deb9u1 : xmlwriter v7.0.30-0+deb9u1 : xsl v7.0.30-0+deb9u1 : Zend OPcache v7.0.30-0+deb9u1 : zlib v7.0.30-0+deb9u1
Client Information
HTTP Browser Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.1 Safari/605.1.15
Screen Resolution 1680 x 1050
Window Size 1480 x 870
(Paul) #2

See Backup Option not available this came up a few days ago and applies to the sync module and the post-process module too, there maybe others, I’m not sure I didn’t check them all.

Thanks for letting us know anyway, the more it’s discussed the more likely users are going to find the solution or maybe even be aware when it happens.