Package Details: monitorix 3.8.1-2

Git Clone URL: (read-only)
Package Base: monitorix
Description: A lightweight system monitoring tool that uses rrd databases.
Upstream URL:
Licenses: GPLv2
Conflicts: monitorix-git
Submitter: None
Maintainer: graysky
Last Packager: graysky
Votes: 88
Popularity: 1.409698
First Submitted: 2010-01-24 13:53
Last Updated: 2016-02-02 08:06

Dependencies (17)

Required by (0)

Sources (1)

Latest Comments

harveythedog commented on 2016-02-02 02:36

Got an error when building: "conflicts should be an array"


changed to


and everything built OK?

graysky commented on 2015-11-13 19:20

Bump to v3.8.1-1

graysky commented on 2015-05-29 22:23

Bump to v3.7.0-2

Changelog: Include fix for broken rrdtool referenced by cgirard.

cgirard commented on 2015-05-21 16:18

FYI the system graph is broken since the update to RRDTool 1.5. It will be fixed in the next version:

harveythedog commented on 2015-04-19 04:10

After installing, in monitorix.conf, I had to change: base_cgi = /monitorix-cgi

to: base_cgi = /monitorix/cgi/

Otherwise my /monitorix base url would 404 when I tried to select and view a graph page (daily,weekly etc.)?

Probably user error....

sudosoldier commented on 2015-03-12 17:25 now 404s, please update to 3.7.0.


graysky commented on 2014-09-29 09:37

You should report this upstream. Use Jordi's github page to crate an issue.

hbc2 commented on 2014-09-29 07:15

All graphs in Processes Statistics render fine except for Open Files "z" images. The small "non-z" images are generated, just not the z image.

This is the message that appears in the browswer:
ERROR: while graphing /srv/http/monitorix//imgs/process05z.1week.png: parameter 'wrongdata' does not represent a number in line AREA:wrongdata#FFFFFF

graysky commented on 2014-08-23 09:07

@Bruiser - Try 3.6.0-3 which should fix it.

BruiserBrody17 commented on 2014-08-23 02:22

Doing a clean install of 3.6.0 results in the systemd service not starting. Starting it manually gives me errors. Here is the log

graysky commented on 2014-08-20 20:11

Bump to v3.6.0-1

milouse commented on 2014-08-10 17:50

Oupss. I spoke too fast. I CONFIRM the dependancy on perl-dbd-mysql. With it, monitorix works as expected. I must have waited a bit before posting my previous comment, in order to let monitorix get first data from mysql.

However, without it you still get the same error messages as I reported before (I wait a night without seeing anything coming before looking in the logs).

Thus, I don't think it is a relevant issue to report upstream. You should just add perl-dbd-mysql in the PKGBUILD as a dependancy, or just as an optdepends, saying for exemple ('perl-dbd-mysql: enable support for mysql/mariadb monitoring').

Finally, I should be wrong saying that, but perl-dbd-mysql depends on perl-dbi. If it is not directly required by monitorix for other stuff, you maybe could remove it from the dependancies (as it will come with perl-dbd-mysql, either mandatory or optional dep.).

graysky commented on 2014-08-10 17:19

@milouse - Open an issue on the github page:

milouse commented on 2014-08-10 15:53

@berot3 you should have done the same mistake as me : reading doc too fast and trying to access monitorix on http://localhost:8080. In fact only the perl server listen there, monitorix is available at http://localhost:8080/monitorix

Oh, and by the way @graysky, it seems that perl-dbd-mysql is a dependancy (several error messages in monitorix logs : Sun Aug 10 17:41:01 2014 - mysql_update(): install_driver(mysql) failed: Can't locate DBD/ in @INC (you may need to install the DBD::mysql module)). But even with this installed, I cannot reach to have mysql graph working (graph stay empty with NaN value...). If someone has an idea about it...

milouse commented on 2014-08-09 17:12

@berot3 you should have done the same mistake as me : reading doc too fast and trying to access monitorix on http://localhost:8080. In fact only the perl server listen there, monitorix is available at http://localhost:8080/monitorix

graysky commented on 2014-07-11 18:58

I just tested lighttpd + monitorix and it works for me out-of-the-box without any tweaks.

berot3 commented on 2014-07-11 10:22

Am I the only one who needs to a ln -s monitorix/cgi/ monitorix/monitorix-cgi?
Else-wise I only get a 404...

Schmeidenbacher commented on 2014-06-07 20:22

Hold your horses. I'm just a big dummy.

It's only on the frigging Raspberry Pi.

I use archlinuxarm on that one, and they seemingly haven't rebuild rrdtools yet.

Sorry for that.

Schmeidenbacher commented on 2014-06-07 20:14

Actually, that was the first thing i tried, but no luck.

In the meantime i found the logfile.

Sat Jun 7 22:12:02 2014 - WARNING: unable to load module 'system'. Perl API version v5.18.0 of RRDs does not match v5.20.0 at /usr/lib/perl5/core_perl/ line 216.
Compilation failed in require at /usr/lib/monitorix/ line 26.
BEGIN failed--compilation aborted at /usr/lib/monitorix/ line 26.
Compilation failed in require at (eval 8) line 1.
BEGIN failed--compilation aborted at (eval 8) line 1.

Afterwards all monitorx modules fail at line 26, which would import the RRDs module.

But that makes no sense, rrdtools, from which the RRDs module is from was rebuilt together with perl 5.2, i checked the dates.

graysky commented on 2014-06-07 20:08

Have you rebuilt perl-config-general?

Schmeidenbacher commented on 2014-06-07 19:48

Mmmh. I just noticed that after the perl update to 5.20 monitorix won't start anymore.

The problem is, that it doesn't give me any error message at all. Does anyone have an idea what's up with it?

SanskritFritz commented on 2014-05-18 10:35

Thanks for the heads-up, I think you're right.

graysky commented on 2014-05-18 10:33

@San-Yes, due to upstream's moving of the config file... I think that if I remove that from the backup array, then users coming from older versions will not have their live config files backed-up when updating.

SanskritFritz commented on 2014-05-18 10:26

==> WARNING: backup entry file not in package : etc/monitorix.conf

graysky commented on 2014-05-18 09:53

Bump to v3.5.1-2

Changelog: Updated install path of docs per bidulock's suggestion.

bidulock commented on 2014-05-18 09:43

3.5.1-1 should not be installing documentation files in /usr/share/doc as you are doing in package(): they should go in /usr/share/doc/${pkgname}

graysky commented on 2014-03-24 20:21

Bump to v3.5.0-1

Note the change from /etc/monitorix.conf --> /etc/monitorix/monitorix.conf in this version. Pacman should backup your old config file to /etc/monitorix.conf.pacsave and you should then therefore diff it and merge into /etc/monitorix/monitorix.conf with a util like vimdiff or whatever.

graysky commented on 2013-12-15 17:59

Not sure what you mean... if you believe you found a bug, please contact the author. You can create a new issue on github:

linusfan commented on 2013-12-15 17:34

After installation and configuration functions obtained after pressing "OK" on the home page a new page with a "404 - Not found". The CGI path in /srv/http/monitorix/index.html is incorrect and should read: <form action="cgi/monitorix.cgi" method="get">

graysky commented on 2013-12-07 12:20

Bump to v3.4.0-1

graysky commented on 2013-11-26 23:42

Bump to v3.3.1-2

graysky commented on 2013-11-26 23:40

Ah, you are correct... should be 'EnvironmentFile'

supersym commented on 2013-11-26 21:53

My journalctl:
[/usr/lib/systemd/system/monitorix.service:8] Unknown lvalue 'EnvironmentFiles' in section 'Service'

Typo. This should be 'EnvironmentFile' probably.

graysky commented on 2013-08-12 21:18

Bump to v3.3.0-1

graysky commented on 2013-06-03 20:15

Bump to v3.2.1-1

graysky commented on 2013-01-12 22:54

Just as an FYI: this PKG will provide the stable release of 2.x while the following package will provide the 3.x series which is currently in beta status. Once the beta status has been removed, I will ask that the 'monitorix-beta' package gets deleted and this one will be updated to the 3.x branch.


graysky commented on 2012-10-10 19:13

@DF - OK. I have modified the service file per your suggestion. Thank you!

DerFlob commented on 2012-10-10 18:32

No, ExecStop is optional. By default systemd will send a SIGTERM to the process when stopping (and a SIGKILL after a timeout when the process doesn't exit).

graysky commented on 2012-10-10 17:44

@DerFlob - doens't it need a ExecStop as well?

graysky commented on 2012-10-10 17:43

@DerFlob - thank you. does that code work on your pure systemd machine?

DerFlob commented on 2012-10-10 16:49

The service-file doesn't work on a clean systemd installation without initscripts.
I am by no means an expert for systemd, but this is a working [Service] section for me.

ExecStart=/usr/bin/monitorix -c /etc/monitorix.conf -p /run/

graysky commented on 2012-09-22 16:02

Bump to v2.6.0-1

graysky commented on 2012-05-23 20:33

Bump to v2.5.2-1

graysky commented on 2012-04-24 20:50

Bump to v2.5.1-1

graysky commented on 2012-03-22 11:11

Bump to 2.5.0-1

Also rebuilt the PKGBUILD to use install rather than cp.

graysky commented on 2012-03-22 00:24

I know that 2.5.0 is out but I am in email discussion with Jordi to fix a problem before bumping this PKGBUILD.

graysky commented on 2012-01-20 21:51

Bump to 2.4.1-2
Changelog: added new dep, thanks to lennard200

graysky commented on 2011-12-18 11:33

Bump to 2.4.0-2
Changelog: added optdep and minor changes to PKGBUILD

graysky commented on 2011-11-29 08:28

Update to 2.4.0. Changelog @
New features added that require you to diff your /etc/monitorix.conf against /etc/monitorix.conf.pacnew after installing!

graysky commented on 2011-11-28 23:19

Update to 2.4.0. Changelog @

harveythedog commented on 2011-11-15 22:24

Cheers graysky - All fixed!

And to think how ever-so-slightly sceptical I was, considering the complete lack of Nvidia GPU's in use :)


graysky commented on 2011-11-15 18:04

OK... the problem is with the 285.xx version of the nvidia dirver. Here's what Jordi said, "I can't give support to this new driver version 285.+ now.

So in order to work-around the issue please, remove the last entry in your %SENSOR_LIST array ('GPU0'), and you shouldn't see the 'divide by zero' error message anymore.

I'll try to include its support as soon as I can have such driver here and can play a bit with it.

Please, let me know if the work-around worked.
Many thanks."

harveythedog commented on 2011-11-13 23:59

Thanks for the info graysky. I'm not losing my marbles then :)

graysky commented on 2011-11-13 17:43

I get the same thing, harvey- emailed Jordi

harveythedog commented on 2011-11-09 00:02

Anyone having trouble with the lm_sensors graph since updating to 2.3.0?? New/updated monitorix.conf: check....nice data from $sensors....I'm out of ideas.

From the log:
lmsens_update(): Illegal division by zero at /usr/bin/monitorix line 1368.

graysky commented on 2011-09-25 19:18

Update to 2.3.0. Changelog @
Also fixed /etc/rc.d/monitorix (thanks falconindy)

graysky commented on 2011-06-24 19:13

Update to 2.2.0. Changelog @

graysky commented on 2011-05-04 19:36

Updated to 2.1.2. Changelog @

scar commented on 2011-03-27 13:45

Thank you, it works now.
( sorry for the delay, I had a hedgehog-like flu in my throat for a couple of weeks )

graysky commented on 2011-03-11 18:51

@scar - mine typeo on my part. Try 2.1.0-2 and let me know. It worked on a virgin install in a chroot for me.

scar commented on 2011-03-10 23:32

You know, I1m the guy who makes you crazy.
Monitorix is not working for me at all. Fresh install, x86_64 arch, followed the wiki, and all.
When starting the service, nothing happens.
#ps aux | grep monitorix shows nothing.
lauching by : " #monitorix -d -c /etc/monitorix " shows nothing
Absolutely nothing happens.

graysky commented on 2011-03-10 00:12

Updated, thanks for the heads-up.

scar commented on 2011-03-09 23:04

please update to 2.1.x-x

maggie commented on 2011-02-12 13:54

Nice tool. Thak you for making this pkg.

graysky commented on 2011-02-01 02:01

Now we're at 2.0.0
Remember to delete your current files (below) for this upgrade!

/var/lib/*.rrd # databases
/etc/monitorix.conf # config file

I suggest using vimdiff to edit the config file if you have anything special in there from 1.5.2 that you want to transition but know that many of the variables have changed!

graysky commented on 2011-02-01 02:00

Now we're at 2.0.0
Remember to delete your current .rrd databases for this upgrade!

graysky commented on 2011-01-26 21:00

Your package monitorix has been flagged out of date by ashren [1]. You
may view your package at:

@ashren - 2.0 hasn't been released yet. I have been helping Jordi to test 1.9.4 (beta) and it's running very well now. He plans to release 2.0 shortly at which point I will update this PKGBUILD.

graysky commented on 2010-11-18 19:31

Updated to 1.5.2 - minor bug fixes per the changelog.

scar commented on 2010-08-06 15:43

thanks for the reply, more on the thread

graysky commented on 2010-08-05 06:42

I replied to you in that thread.

scar commented on 2010-08-04 18:45

I've installed but had to voodoo around to find the cron job, because it was not installed by default

forum link here:

graysky commented on 2010-07-08 23:32

Good idea... done.

cdemoulins commented on 2010-07-08 11:21

Maybe a solution could be to add a message or an optional dependency to explain that a mono-font is needed like terminus-font.

graysky commented on 2010-07-08 08:47

@cdemoulins - I think that any monospaced font will work.

Have a look at and if you can figure it out, please post there too :)

cdemoulins commented on 2010-07-08 08:45

Hi, there is a reason to not add "terminus-font" has dependency ?

graysky commented on 2010-06-27 14:39

Updated to 1.5.1

graysky commented on 2010-05-22 11:24

If you like monitorix, have a look at monitorix-tmpfs (here in the AUR) which is a simple bash script to allow monitorix to run in /dev/shm and sync data back to your hdd. It will dramatically reduce hdd writes when the databases get updated.

graysky commented on 2010-05-22 11:09

If you like monitorix, have a look at monitorix-tmpfs (here in the AUR) which is a simple bash script to allow monitorix to run in /dev/shm and sync data back to your hdd. It will dramatically reduce hdd writes when the databases get updated.

graysky commented on 2010-05-02 08:06

Updated to 1.5.0 - make sure you do NOT use your old /etc/monitorix.conf with this update!

graysky commented on 2010-04-08 23:26

Updated. Please give it a try and let me know that it's 100 %

Anonymous comment on 2010-04-08 08:08

version 1.5.0 is out.