I often use it to scan for plugins in the Drupal codebase or to scan through a CSV or log file for data. For example, to scan for user centric ViewsFilter plugins in the Drupal core directory use this command assuming you are relative to the core directory. The -r flag here recursively scans the 'core' directory. This command returns the following output. Part of the process of putting a new site live can be moving DNS entries around.
It's also very important to check the status of your DNS records to ensure that they have the correct TTL, usually a day before and day of the move. Whilst it is possible to view the contents of an SSL cert from within most modern browsers I occasionally find the need to use the command line to find out the same information. I find this useful when renewing certificates as browsers can occasionally cache certificates for longer than expected, causing false results.
The following command connects to the server, downloads the SSL certificate from port and then uses the openssl tool to extract the information from the certificate into a readable format. Share this Tweet this Share this When Munin does a data update it stores all of the data from the nodes as a set of rrd files. Munin: This RRD was created on another architecture The problem was that I had moved these files from a 32 bit system to a 64 bit system and this means that the file was unreadable by the new machine due to the different architecture.
Your name. Email The content of this field is kept private and will not be shown publicly. Leave this field blank. It makes it easy to determine "what's different today" when a performance problem crops up.
It makes it easy to see how you're doing capacity-wise on any resources. It then stores the data in RRD files, and if needed updates the graphs. One of the main goals has been ease of creating new plugins graphs.
Plugins are small, standalone executables. They are easy to write, and can be written in any language. What is Munin? Check the demo server. Monitoring within easy reach Complicated does not mean efficient ; easy isn't superficial.
Real-time alerts Munin polls your servers once every 5 minutes. Extensible Write your own plugins in the language of your choice to supervise whatever you want. Maintained Munin's first version was released in and it has kept evolving since.
You should protect against misuse of ssh by creating a special key and possibly also a special user. We are also restricting a few options:. For interface eth0 on host foo. Check that the plugin has no references in munin. If you are installing a wildcard plugin e. So, try to temporarily disable completely the hardening tool. If it works then you need to configure it properly for your plugin.
Just after the hardening tools you might have environment var issues, such as PATH. For that, just use the config syntax env. Yes, you can create a file in the plugin configuration directory client-conf. The file should contain the username and group to run the plugin as. Similarly, you could use the user option to run the plugin as a user. If more than one group is needed, or some of the groups only exist on certain hosts and you want a common config file , the syntax supports this:.
Is it possible to change this interval to an arbitrary value? Changing this default behaviour has been proposed in Ticket 5. Because they are so-called wildcard plugins, which means that the exact same plugin may be used in different contexts or with different resources.
Running the plugin directly with the parameter suggest will hopefully :- output the possible uses for the plugin. The same plugin will be linked to the available interfaces on the system, e. Hard to say. Please refer to debugging munin plugins for a treatment on how to find out. See also the next question:. This again causes the plugin to not find the mysqladmin program which it needs to retrive the numbers the needed in the graphs. The solution is to hardcode the path of the program.
First locate the mysqladmin program. On most systems, the command which mysqladmin , type mysqladmin or locate mysqladmin will help you. Even though all the readings from it are integers, the cur value in munin is showing a floating point number. This is due to the fact that Munin takes a while to collect all the input numbers and therefore the collection of most numbers does not happen at the precise point in time that RRD wants.
When that happens, RRD makes an interpolation between the two last data points. This leads to floating point numbers in the display. GAUGE values are floating point. The most frequent reason for this is that munin.
This is a bug. Please post about your problem on the munin-users list as we have not been able to reproduce the problem. You have to do it manually with :.
0コメント