Skip to main content

Load Statistics graph weird encoding #javamelody #font #font_issue


Problem:

If we deploy our application (*.war) on a customer's infrastructure, all texts in graphs are broken. The very same montioring of the application works when deployed in our local infrastructure. All "plain" texts are rendered corretly.
  • Only graphs are affected
  • The problem seems to be environment specific
I've no clue what we need to do/install/change on the customers environment to be able to have proper texts in graphs again. When we first installed the application the graphs worked. Our customers administrators have updated the system / installed patches since then but cannot tell what they've done exactly. I've never seen java melody showing broken graphs before.
Broken Dashboard:
javamelody_charset_graph_error
Betriebssystem: | Linux, 3.10.0-693.2.2.el7.x86_64 , amd64/64 (16 Kerne)
Java: | Java(TM) SE Runtime Environment, 1.8.0_111-b14
JVM: | Java HotSpot(TM) 64-Bit Server VM, 25.111-b14, mixed mode
Server: | Apache Tomcat/8.0.36
Same Application works fine in our local test environment:
Betriebssystem: | Linux, 4.4.0-78-generic , amd64/64 (16 Kerne)
Java: | Java(TM) SE Runtime Environment, 1.8.0_121-b13
JVM: | Java HotSpot(TM) 64-Bit Server VM, 25.121-b13, mixed mode

Solution:

fc-list
yum install dejavu-sans-fonts.noarch dejavu-sans-mono-fonts.noarch
After installation, restart application.

Comments

Popular posts from this blog

Understanding the dm-multipath Configuration file /etc/multipath.conf #centos7

Understanding the dm-multipath Configuration file /etc/multipath.conf The main configuration file for DM-Multipath is  /etc/multipath.conf . This file is not created by the initial installation of the RPM package. However, the following file is installed in the  /usr/share/doc/device-mapper-multipath-[version]  directory: multipath.conf  – Basic configuration file with some examples for DM-Multipath. This file is used to create the /etc/multipath.conf file. Sample /etc/multipath.conf file The multipath.conf file contains the following sections, and each section contains one or more attributes or subsections. Section Description defaults Defines the default settings for DM-Multipath. These settings can be overwritten by the devices and multipaths sections. blacklist Defines the devices to be excluded from the multipath topology discovery. Devices that are blacklisted are not grouped into a multipath device. blacklist_exceptions Defines the devices to ...

upload file type rocket chat #Accepted file upload. Can not send .xlsx

Enabling File format for upload at ROCKET CHAT application/msword   - for .doc application/vnd.openxmlformats-officedocument.wordprocessingml.document   - for .docx application/vnd.ms-excel   - for xls application/vnd.openxmlformats-officedocument.spreadsheetml.sheet   - for .xlsx application/vnd.ms-powerpoint   - for .ppt application/vnd.openxmlformats-officedocument.presentationml.presentation   - for .pptx image/*,audio/*,video/*,application/zip,application/x-rar-compressed,application/pdf,text/plain,application/msword,application/vnd.openxmlformats-officedocument.wordprocessingml.document,application/vnd.ms-excel,application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

Troubleshooting DRBD #Centos #DRBD

Troubleshooting DRBD  This article presents common DRBD problems and solutions. DRBD (Distributed Replicated Block Device) runs on the master and slave nodes only, and is responsible for mirroring the contents of a partition between master and slave.  Typical problems in DRBD include: A lack of Primary-Secondary connectivity The Secondary operating in standalone mode Both nodes reporting connectivity but neither one in the role of master Both nodes reporting themselves in the role of master Verify the DRBD status The following command is used to verify that DRBD is operating normally on the master and slave nodes. drbd-overview When run on the master node, the output should look like the following: 1:r0/0 Connected Primary/Secondary UpToDate/UpToDate C r----- /mnt/drbd  ... When run on the slave node, the output should look like the following: 1:r0/0 Connected Secondary/Primary UpToDate/UpToDate C r----- The following sections are exampl...