Anonymous

Project:Tool Access Control/ACNet: Difference between revisions

From London Hackspace Wiki
Added troubleshooting info for the acserver
(Added troubleshooting info for the acserver)
Line 9: Line 9:
== TODO ==
== TODO ==
* Add a secondary acnode and test multiple acnode functionality (Sol)
* Add a secondary acnode and test multiple acnode functionality (Sol)
* Figure out a strategy of syncing the membership database to the local access database, as currently manual (mentar)
** Optimise the sync so it takes less time and add it to the cron job to every few minutes
* Move the acserver to a separate VM running on the server downstairs (tgreer + mentar)
* Move the acserver to a separate VM running on the server downstairs (tgreer + mentar)
* Add a way of adding cached tool useage using  POST /[nodeID]/cachedtooluse/[cardID]/[timeUsed]/[timestamp] (mentar + sol)
* Add a way of adding cached tool useage using  POST /[nodeID]/cachedtooluse/[cardID]/[timeUsed]/[timestamp] (mentar + sol)
Line 64: Line 62:
=== Membership DB ===
=== Membership DB ===
Running on Turing VM slice (hosted outside the space as it has personal data). Accessed in JSON format.
Running on Turing VM slice (hosted outside the space as it has personal data). Accessed in JSON format.
=== Troubleshooting ===
The server currently runs in "beta" on babage:1234.
The acserver permission database is synced with our membership database every minute and leaves a heartbeat at /var/log/acserver_update.log. So check the last modified stamp on that and if the heartbeat is returning 1
The application itself is in /var/www/acserver and relies on the local mysql database to work properly also it uses the nginx webserver (leaner, quicker than apache2) so make sure that is running too