I'm running zabbix 4 on EC2 Amazon Linux 2 instance. After last update:
May 29 08:06:46 Updated: zabbix-web-mysql-4.0.8-1.el7.noarch
May 29 08:06:46 Updated: zabbix-web-4.0.8-1.el7.noarch
May 29 08:06:46 Updated: zabbix-get-4.0.8-1.el7.x86_64
May 29 08:06:47 Updated: zabbix-server-mysql-4.0.8-1.el7.x86_64
May 29 08:06:47 Updated: zabbix-agent-4.0.8-1.el7.x86_64
All my dashboards graphs lost text description. Even in host configuration, when I click preview in graph there is no text.
Checked on Chrome and Firefox. Tried to recreate dashboard, cleaned browser cache. I googled that it can be issue with fonts. Checked... Still not solved.
screen_of_my_dashboard
screen_of_graph_preview
Resolved on my 4.2.2.
verify permissions for '/usr/share/zabbix/assets', if not 'www-data:www:data'
chown www-data:www-data assets/
If the file does not exist (/usr/share/zabbix/fonts/graphfont.ttf):
cd assets/fonts/
Copy the file graphfont.ttf to /usr/share/zabbix/assets/fonts/: (source: https://support.zabbix.com/browse/ZBX-16182)
cp /usr/share/zabbix/fonts/graphfont.ttf /usr/share/zabbix/assets/fonts/
Or link the file:
ln -s /usr/share/zabbix/fonts/graphfont.ttf /usr/share/zabbix/assets/fonts/
by, Bruno Dolastro - Br4zil
Related
Ever since I've upgraded my Mac to Monteray, I've been having issues with Vagrant.
Initially, I use to see a vBoxManage error on terminal when running vagrant up. I posted a question on this on SO previously, see here for details.
Today, I uninstalled VirtualBox again (removed VirtualBox VMs folder and moved application to trash) and reinstalled VirtualBox 6.1.3 for OS X hosts` (link here).
I then ran vagrant up on terminal and it successfully compiled:
After seeing the famous green teddy, I tried going to vvv.test but, the page doesn't load. I've tried accessing URLs of sites that have been provisioned before, but they too do not load.
I've also ran vagrant up --debug, and nothing concerning was seen.
My Vagrant version is 2.2.19
Unsure what steps to take next?
Edit:
Steps taken:
Have ran vagrant up --provision to provision sites in config.yml file (config.yml file can be seen below)
Have tried to access website-dev.test, page doesn't load
Have tried to access vvv.test, page doesn't load
Have ran vagrant reload --provision and repeated steps 2 and 3, but same results
Have ran vagrant halt and vagrant up and repeated steps 2 and 3, but same results
I don't believe there's an issue in my config.yml file, as before Monteray update, everything was working fine (and I've made no changes to my yml file since). But, to cover all scenario's, here is my config.yml file:
sites:
website-dev:
skip_provisioning: false
description: ""
hosts:
- website-dev.test
custom:
wpconfig_constants:
WP_DEBUG: true
WP_DEBUG_LOG: true
WP_DISABLE_FATAL_ERROR_HANDLER: true
wordpress-trunk:
skip_provisioning: true
description: "An svn based WP Core trunk dev setup, useful for contributor days, Trac tickets, patches"
repo: https://github.com/Varying-Vagrant-Vagrants/custom-site-template-develop.git
hosts:
- trunk.wordpress.test
wordpress-meta-environment:
skip_provisioning: true
description: "An environment useful for contributions to the WordPress meta team."
repo: https://github.com/WordPress/meta-environment.git
hosts:
- wp-meta.test
custom:
provision_site:
"buddypressorg.test": true
"jobs.wordpressnet.test": true
"wordcamp.test": true
"wordpressorg.test": true
"wordpresstv.test": true
utilities:
core:
- tls-ca
- phpmyadmin
vm_config:
memory: 1600
cores: 2
general:
db_backup: true
db_restore: true
db_share_type: false
vagrant-plugins:
disksize: 10GB
In regards to vagrant ssh, I'm unsure on what steps I would need to take to get vvv.test to start working again here, can't see anything on the docs for this also?
Thanks to guidance from #Tinxuanna, I've managed to solve the issue (finally!).
For anyone else having similar issues, here's what I did:
Access the /etc/hosts folder
Find file called hosts and open it in a text editor.
Remove the IP addresses related to vagrant (I kept a backup of the original file just in case)
After saving hosts file the IP addresses removed, I ran vagrant up --provision
I then ran vagrant up
Then accessed vvv.test
You're done!
After trying the solutions provided by others, I determined that the problem on my machine was a wrong ip range in Vagrantfile. To solve this:
Edit Vagrantfile
Change IP defaults['private_network_ip'] = '192.168.56.4' to different range
Save it and run vagrant up --provision
If Freddy's solution doesn't work, then give this a try.
I wanted to help with one question, but was recieved my own.
Where is a problem?
I tried to repeat some basics from there: https://bookdown.org/yihui/blogdown/a-quick-example.html
all instructions were followed and fulfilled;
hugo was downloaded and installed;
site was launched by blogdown::serve_site().
It works! But...
Launching the server via the command:
C:/Users/User/AppData/Roaming/Hugo/0.89.4/hugo.exe server --bind 127.0.0.1 -p 4321 --themesDir themes -t hugo-lithium -D -F --navigateToChanged
Serving the directory . at http://localhost:4321
Launched the hugo server in the background (process ID: 1780). To stop it, call blogdown::stop_server() or restart the R session.
... look, where is a message??? (as you can see there):
Rendering content/post/2020-12-01-r-rmarkdown/index.Rmd... Done.
Ok, I tried to add content to index.Rmd:
```{r}
summary(Orange)
```
And, after saving, we can see this message:
Again these hellish replacement symbols and (Sys.setenv("LANGUAGE"="EN") didn't help, but this isn't a story about them).
How to fix this problem with index.Rmd in blogdown? Maybe someone faced with it?
Very grateful for the help.
And a little addition.
I deleted and recreated "my website".
This string was displayed...
Rendering content/post/2020-12-01-r-rmarkdown/index.Rmd... Done.
... but error is the same ...
This answer is for the future sufferers and thoughtless persons (as I am):
Guys, we shouldn't touch the "index.Rmd" in the main directory of our site's folder!
Am I right?
Some proposals to Yihui Xie:
Why "the main index.Rmd" can't have an other name, f.e.:
mainIndex;
primaryIndex;
baseIndex;
etc...
... and it will be nice, if you add to this file some info, f.e.
<!-- If you want to add some new info to your site - come to "content - post - bla-bla - index.Rmd" -->
<!-- Please don't try to edit the current file -->
---
site: blogdown:::blogdown_site
---
Or nevertheless someone can add something and save after "index.Rmd"?
I do not see Thumbnail for the image type ( png ) in the Document Library.
I see properly the Thumbnail of PDF and DOC
Other error when i try to change Alfresco Icon:
Unsupported transformation: transformer.ImageMagick image/png to image/png
imagemagick version: 7.0.5-2
Configuration in global properties:
### External executable locations ###
ooo.exe=E:/alfresco-community/libreoffice/App/libreoffice/program/soffice.exe
ooo.enabled=true
ooo.port=9100
img.root=E:\\alfresco-community\\imagemagick
img.dyn=${img.root}\\lib
img.coders=${img.root}\\modules\\coders
img.config=${img.root}
img.exe=${img.root}\\convert.exe
alfresco-pdf-renderer.root=E:\\alfresco-community\\alfresco-pdf-renderer
alfresco-pdf-renderer.exe=${alfresco-pdf-renderer.root}\\alfresco-pdf-renderer.exe
Please, help
SOLVED
I think that the Imagemagick inside the Alfresco-community release has a bug.
Imagemagick version: 7.0.5-2
I installed last version with all flags during installation wizard ( NOT for associate files to ImageMagick )
Config in global properties:
img.root=C:\\ImageMagick-7.0.8-Q16-HDRI
img.coders=${img.root}\\modules\\coders
img.config=${img.root}
img.exe=${img.root}\\convert.exe
img.dyn=${img.root}\\lib
http://www.imagemagick.org/script/download.php#windows
My issue was that alfresco-pdf-renderer was not working in linux (only for txt, ftl,html mimetypes). It was working for other mimetypes. Also, it was working in windows for all mime types:
I resolve it on my linux envt by:
Changing the owner of 'alfresco-pdf-renderer' file from ec2-user to root
sudo chown root:root alfresco-pdf-renderer
Share admin console properties set at http://hostname:8080/alfresco/s/enterprise/admin/admin-transformations:
/app/alfresco/alfresco-pdf-renderer
/app/alfresco/alfresco-pdf-renderer/alfresco-pdf-renderer
Imagemagick was already enabled and working fine in my case. Also if above solution does not work, you can try out this - https://hub.alfresco.com/t5/alfresco-content-services-forum/how-do-i-integrate-alfresco-pdf-renderer-in-the-community/td-p/218405
I received a project and I'm trying to start it in Docker with NGINX environment. But it seems I have a bug with LiipImagine. The project use Symfony 4 and LIIPImagine version 2.0.x-dev.
A page should display images from cache, exemple of an image URL :
https://localhost:8443/media/cache/live_feed_message/images/live_feed_message/5c486df1a78fe_lama-750389_960_720.jpg
The directory exists with rights :
drwxr-xr-x 2 1000 1000 4069 Jan 23 13:35 live_feed_message
All images are stored in public/images/live_feed_mesage/ and in public/media/cache/live_feed_message/images/live_feed_message the corresponding image doesn't exists.
I figured out that if I use the command from LiipImagine:
php app/console liip:imagine:cache:resolve relative/path/to/image1.jpg
It gives this result :
http://localhost/media/cache/quizz_thumbnail/images/live_feed_message/name_file.jpg
http://localhost/media/cache/quizz_sponsors_icon/images/live_feed_message/name_file.jpg
http://localhost/media/cache/live_feed_message/images/live_feed_message/name_file.jpg
And then the corresponding image exists in cache (public/media/cache/live_feed_message/images/live_feed_message) and the image displays correctly on the page...
In network tab from development console, I checked the response from an HTTP request. And I get this Symfony response:
Unable to write to the "/srv/api/public/media/cache/live_feed_message/images/live_feed_message" directory.
Does someone know what could be the issue ?
Since 2 days I can't resolve this issue, so thanks for your help !
PS: I overrided a route from routing.yaml from the bundle.
In the path there was /resolve and I overrided with this (in fact I deleted /resolve from liip_imagine_filter path):
_liip_imagine:
resource: "#LiipImagineBundle/Resources/config/routing.yaml"
liip_imagine_filter:
path: /media/cache/{filter}/{path}
defaults:
_controller: '%liip_imagine.controller.filter_action%'
methods:
- GET
requirements:
filter: '[A-z0-9_-]*'
path: .+
You should maybe try being more permissive with chmod -R 777 public/images. In local it's not a very big deal, it's in production that you should fine tune your permissions. That would probably clear out your errors and you could go on coding.
An actual permission for production would be 755 IIRC.
We're running nexus on some old hardware which is limited in disk space and would like to remove artifacts older than a certain threshold.
Is there any way to do this other than a combination of find and curl?
There is a scheduled task that can automatically remove old snapshot releases:
http://www.sonatype.com/people/2009/09/nexus-scheduled-tasks/
http://www.sonatype.com/books/nexus-book/reference/confignx-sect-managing-tasks.html
Unfortunately, this does not work for hosted release repositories.
As mentioned on a Sonatype blog post linked from a comment in the blog in gavenkoa's answer, since Nexus 2.5 there is a built in "Remove Releases From Repository" scheduled task which can be configured to delete old releases keeping a defined number.
This is sufficient to meet our needs.
Delete all files to which no one access more then 100 days and not modified more then 200 days:
find . -type f -atime +100 -mtime 200 -delete
To cleanup empty directories:
find . -type d -empty -delete
Or alternatively look to https://github.com/akquinet/nexus_cleaner/blob/master/nexus_clean.sh and corresponding blog entry http://blog.akquinet.de/2013/12/09/how-to-clean-your-nexus-release-repositories/ (delete all except last 10 releases).
auto purge older than 30 days(u can change it) not download docker images from nexus 3
https://gist.github.com/anjia0532/4a7fee95fd28d17f67412f48695bb6de
# nexus3's username and pwd
username = 'admin'
password = 'admin123'
# nexus host
nexusHost = 'http://localhost:8081'
# purge repo
repoName = 'docker'
# older than days
days = 30
#change and run it
For Nexus2, you can use my Spring Boot application https://github.com/vernetto/nexusclean , you can define rules based on date and on a minimum number of Artifacts to retain, and it generates "rm -rf" commands (using the REST API is damn slow).
For Nexus3, I would definitely use a Groovy script as a "Execute Admin Task". One is posted here groovy script to delete artifacts on nexus 3 (not nexus 2)