Directory "/usr/share/zabbix/assets" must be writable.

[tsvyake]

Hello Dear All, i try install Zabbix server on Centos 7(Zabbix 4.0.8) .but when start Zabbix Frontend i get error i try fix it ( sudo chmod -R 777 /usr/share/zabbix/assets; chown zabbix:zabbix /usr/share/zabbix/assets;chown -R nginx:nginx /usr/share/zabbix/assets but same result

[tsvyake]

Hello All,solved me

chown -R nginx:nginx /usr/share/zabbix/assets/
semanage fcontext -a -t httpd_sys_rw_content_t ‘/usr/share/zabbix/assets’
restorecon -vvR /usr/share/zabbix/assets

[mbuyukkarakas]

Hello, thanks for information.
Do you see any graphic problem ? Most of us faced at graphics created from latest data, no legend problem.

Mehmet

[kloczek]

Those per session/user data should be written in DB backend and if not it is nothing more than asking for troubles.
Hopefully this issue will be fixed soon.

[onionsgalore]

I am having this same issue too, starting yesterday. Installing 4.2.1 on a Raspberry Pi

[onionsgalore]

So I was poking around in the various directories for zabbix, and noticed that the /usr/share/zabbix/ directory that I downloaded after June 1st was different than the ones prior. I didn't see anything about an update going out, so I copied the whole directory and permissions from a known working zabbix install (4.2.1) and replaced it on my non functional install. I was able to complete the installation and so far there aren't any issues.

So this isn't a permissions issue at all, I think zabbix is trying to write to a directory that doesn't exist.

e: I did also have to manually upload the zabbix.conf.php file, but the installer seemed to expect this to be an issue and provided instructions on how to do it easily. I will update this thread if anything else breaks lol.

e2: I overlooked the fact that the old /usr/share/zabbix/ directory doesn't have an assets folder at all... very strange.

e3: looks like 4.2.2 did release on the 27th... is zabbix-release_4.2-1+stretch_all.deb still the latest package?

[p0wertiger]

It looks like packaging issue. I fixed my assets dir previously and today after package upgrade on CentOS 7 the issue returned. Upgrade notes for 4.2.2 state "Write permissions to the assets directory are now required for the web server user." but the packages aren't probably setting this up properly. In my case I changed the ownership of assets dir to webserver user. Given that the dir is now writable by webserver it should be moved outside of /usr/share, probably somewhere around /var/lib.

[onionsgalore]

Looks like this issue was resolved in 4.2.3

[mbuyukkarakas]

I also updated my system to 4.2.3. The directory permission problem and ugly graphics are solved.