I am trying to use this to monitor hdd health:
https://share.zabbix.com/storage-devices/smartmontools/smart-monitoring-with-smartmontools-lld
I have followed the steps for the agent and server (at least that is my understanding) and would like to know how can I check the monitoring status. even though I might only get an alert in the dashboard if something goes wrong, I would like to see the current status, understand if monitoring is working and everything is ok.
I have followed the linux agent installation steps here: https://github.com/v-zhuravlev/zbx-smartctl
I have also imported the template on the zabbix frontend, and associated the template with the server being monitored.
What now? How can I check if this is working? It seems like there is something missing, but I am not sure where or how to check.
UPDATE:
I am using this template (which mentions Zabbix 3.4) even though I am using Zabbix 4. Since the template in Zabbix Share mentioned it was compatible with 3.4+, I assume this is not an issue: https://github.com/v-zhuravlev/zbx-smartctl/blob/master/Template_3.4_HDD_SMARTMONTOOLS_2_WITH_LLD.xml
Now you should go to "Latest data" and select your server as a host.
You will get the list of the discovered items where you will find the items related to the disk health.
Then, try to select an item and build with it a graph for example and put it in a dashboard.
Related
I installed mosquitto on my Raspberry Pi.
I installed the MQTT Binding, MQTT Binding (1.x) using PaperUI.
I created an item:
Number mqtt_kitchen_gas "Gas Level [%.1f]" {mqtt="<[mosquitto:Home/Floor1/Kitchen/Gas_Sensor:state:default]"}
I opened a terminal window and sent:
mosquitto_pub -u openhabian --pw xxxx -t "Home/Floor1/Kitchen/Gas_Sensor" -m 10
The value "10" appeared in the Gas Level field.
I could change "10" to any number and that would appear in the field.
All was good with the world.
Then I rebooted and looked for the binding MQTT. It is not listed under Configuration, Bindings. (GPIO, another binding I installed is listed.) Also, if I search the Add-ons for MQTT it shows MQTT Binding (1.x) is installed (can be uninstalled) and I can still change the Gas Level field using the above mosquitto_pub.
Maybe I shouldn't worry about it since it works but maybe I have something wrong with my installation and it will come back to bite me.
Any opinions?
I am not completely sure (about 75% :D), but i think that the MQTT 1.x Binding simply doesn't provide any configuration that could be done in paper ui.
That could be the reason why it isn't displayed in the config section.
Since it appears in the addons section and works, everything should be fine.
I am using this binding too and it works properly for ages.
Of course i checked my configuration area in paper ui and it isn't shown there for me too.
Anyways its always fine to check the logs regularly for problems.
If there are none, installation is fine.
We tried to load scripts but something went wrong.
Please make sure that your network settings allow you to download scripts from the following domain:
https://aid-frontend.prod.atl-paas.net/atlassian-id/front-end/4.5.0
Tried Google Chrome, Firefox, Internet explorer also tried with different PC.
Not able to login into bitbucket
I'm using Chrome Version 77.0.3865.120 (Official Build) (64-bit). I got the same error trying to log in to my group's Atlassian site, and I was able to fix it by specifically allowing JavaScript from Atlassian:
Open Chrome settings
Click on Advanced
Click on Privacy and Security
Click on Site Settings
Click on JavaScript
Make sure JavaScript is set to allowed
Next to Allow, click Add
Paste the URL from the error message in and click Add
I've faced a similar problem recently while traveling and trying to work from a new location.
First I've tried the steps from the previous answer which unfortunately didn't help me (but they definitely may be useful in a different case scenario).
I'm renting a house with an existing pre-configured WIFI router which I could get an access to manage it over the web UI.
I'm not sure which of the following helped me. I did the following changes to the router configuration:
Added the 8.8.8.8 as a primary DNS Server
Enabled IPV6
Disabled the built-in firewall (this one is the more likely one which fixed the issue)
I am using Umbraco 7.5.2, installed on a VM in Azure.
When a Publish At date is set, the page is never published. I have tried the following steps.
Create and publish a page
Unpublish the page
Set the Publish At date to a few minutes in the future and Save&Publish
Verified page is definitely not visible
Wait for the time to roll around, and even a few minutes more
Page is never published.
The following message appears in the logs on save when setting the publish at date, which is normal. But no other messages appear after and the page is never published.
2016-10-25 17:46:20,784 [P4808/D10/T21] INFO Umbraco.Core.Services.ContentService - Content 'Video1' with Id '1312' is awaiting release and could not be published.
I've made a copy of my production Umbraco folder and of the database ON THE SAME VM. That instance works for scheduled publishing.
I'm wondering if anyone can provide some clues as to what the issue could be or where I could look. I'd like to avoid having to migrate my production data to this test site.
Thanks
The problem may be related with different time-zone on azure VM as Umbraco is using server time to proceed inside the code execution. This should be the first thing to check.
In version 7.6.0 (https://our.umbraco.org/contribute/releases/760) it will be possible to set up server timezone and then set up a time with precise offset, so those type of problems shouldn't be seen then.
For me it was a wrong umbracoApplicationUrl path (it has to point to YOURDOMAIN/umbraco) After fixing this url everything started working fine
In addition to Marcin's answer, also check that the server can access itself, as it pings itself to fire the scheduled publishing. If it can't resolve it's own address, the scheduled publish will fail. It doesn't happen often, but I've seen a few VERY locked down installs where the server can't resolve it's own address.
We have used Google Cloud Print Service for a few years now, very successfully. Periodically we have issues with print jobs failing, where restarting the Cloud Print Service and the Print Spooler will fix it. That is not the case today.
Today, I am able to print directly to the printer, both from my computer and from the server where we host Google Cloud Print Service. When I attempt to print from Google Cloud Print, I see the print job appear in the queue on the server, and then disappear, and in the Cloud Print queue it simply says "error" with no details on what is happening.
I restarted the print service with logging enabled, attempted to print again, and checked the debug log, with no details present. I'm stumped.
EDIT: After finding the correct debug log, I see this:
CP_CONNECTOR: Job failed (spool failed)
Has anyone dealt with this before, or know of a solution?
Things I have already tried:
Re-connecting Cloud Print Service to our Google account
Re sharing all printers
Reinstalling Cloud Print Service
Restarting the server
Reinstalling printers
After doing many many things, and finally getting Google support on the line, we determined it was a glitch in the Cloud Print Service. The work around, which I was unaware of, and the reason I'm posting this answer, was to use the Chrome Connector.
You can get to that by visiting chrome://devices and then sharing the printers through that form, which looks identical to the one that you get with the Cloud Print Service. I recommend clearing your printer list from Cloud Print first, so you don't get confused.
Once you've shared them, you can then share the printer through Cloud Print just as you would have before.
The only caveat, and the reason this is a work around and not a fix, is that you have to maintain an open Chrome session, meaning you have to keep chrome open for the printers to work. That's fine for us, as there is always a chrome tab open on the server anyway, but it may not work for you long-term.
I have installed the Beta version of chrome, and it seems to resolve the issue. I had this issue on 3 of my 11 servers. All where running stable versions. It was odd that only 3 where not allowing google to print. Once I installed the 64bit beta version, I was able to print. As long as the server was running the Version 53, people could print. It did not matter if someone had a version 52 on there computer. Hope this helps.
I have been working on restoring a build server (tfs 2012) from a backup and all manner of things got messed up (the tfsservice account password had been altered and I had to go to every service and app pool on the box and update it). Once sql was backup I was able to update the password via the TFS admin console app. Then I was able to re-register the build service and add a controller and a build agent. It starts briefly and shows green for a few seconds before stopping and a "details ..." button appears next to the Build Service. If I click the details button I see the following
"Please contact your administrator. There was an error contacting the server. Technical information (for administrator): HTTP code 500: System.ServiceModel.ServiceActivationException"
I have checked the http bindings in iis for the tfs site and there is only the one "*:8080"
I tried hardcoding it to the ip on the box and I still get the same error. If I go to one of the client machines and try and queue a build it shows the build server as being offline.
I have also checked for multiple host headers and the memory utilization which are the most common responses to this particular issue. Neither of them seem to be the cause or the solution.
Any ideas or suggestions are welcome I have run out of ideas to try here. Thanks in advance for any help you have to offer.
EDIT -- also found this in the log: Build machine MyMachine lost connectivity to message queue tfsmq://buildservicehost-25/.