service-discoverd a...
 
Notifications
Clear all

service-discoverd and prometheus permission denied

3 Posts
3 Users
0 Reactions
1,012 Views
(@andreluizpr)
Joined: 1 year ago
Posts: 1
Topic starter  

Hello,

 

I did a fresh install of Carbonio CE on a Linux Ubuntu 20.04 and the whole process went well and apparently everything is working. Analyzing the logs (syslog), something caught my attention and intrigued me:

service-discoverd[7066]: 2023-07-06T13:33:39.827-0300 [ERROR] agent.http: Request error: method=GET url=/v1/agent/self from=127.0.0.1:38104 error="Permission denied"
prometheus[984]: ts=2023-07-06T16:33:39.827Z caller=consul.go:293 level=error component="discovery manager scrape" discovery=consul msg="Error retrieving datacenter name" err="Unexpected response code: 403 (Permission denied)"

The other logs generated in this file are of the info and debug type, which I believe are normal, but this error is generated.

How to fix it? What impact does this bring to my environment if I ignore it?

Thanks,

André


   
Quote
(@0x3f8)
Joined: 1 year ago
Posts: 5
 

Did you ever solve this?   I've done a clean install with a ZCS migration over the weekend and also noticed this error in the logs.  Figured I'd check the forums first before digging too much into 

Other errors include

 service-discoverd[1908]: 2023-10-11T21:25:39.775Z [ERROR] agent.http: Request error: method=GET url=/v1/agent/self from=127.0.0.1:59044 error="Permission denied"

and

Oct 11 21:23:15 mx0 carbonio-prometheus-mysqld-exporter[495]: ts=2023-10-11T21:23:15.763Z caller=exporter.go:149 level=error msg="Error pinging mysqld" err="Error 1045: Access denied for user 'zextras'@'localhost' (using password: YES)"

I don't expect those to be rocket science to fix, but, obviously if there's already a known solution or they're expected, why dig, right?

I think a lot of other errors I'm seeing, e.g.

Oct 11 19:52:33 mx0 saslauthd[4722]: zmpost: url='https:/sampledomain.xyz:7073/service/admin/soap/' returned buffer->data='<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><context xmlns="urn:zimbra"/></soap:Header><soap:Body><soap:Fault><soap:Code><soap:Value>soap:Sender</soap:Value></soap:Code><soap:Reason><soap:Text>authentication failed for [webmaster]</soap:Text></soap:Reason><soap:Detail><Error xmlns="urn:zimbra"><Code>account.AUTH_FAILED</Code><Trace>qtp688593710-1638:1697053953038:f8c4befbe7383ccc</Trace></Error></soap:Detail></soap:Fault></soap:Body></soap:Envelope>', hti->error=''
Oct 11 19:52:53 mx0 postfix/smtpd[245634]: auxpropfunc error no mechanism available
Oct 11 19:58:04 mx0 postfix/submission/smtpd[248863]: auxpropfunc error no mechanism available
Oct 11 20:07:13 mx0 postfix/smtpd[254248]: auxpropfunc error no mechanism available
Oct 11 20:11:22 mx0 postfix/submission/smtpd[256750]: auxpropfunc error no mechanism available
Oct 11 20:11:22 mx0 postfix/submission/smtpd[256750]: SSL_accept error from 66-175-214-19.ip.linodeusercontent.com[66.175.214.19]: lost connection
Oct 11 20:16:59 mx0 postfix/submission/smtpd[260552]: auxpropfunc error no mechanism available

are probably related to spammers/hackers so those are just a matter of tuning up fail2ban and my firewall rules.  Remember kids!  Good passwords and firewall hygiene!

 

 

 


   
ReplyQuote
(@lilokzxtrs)
Joined: 12 months ago
Posts: 3
 

Hello, i also noticed those errors in syslog:

Nov 29 11:31:07 carbonio service-discoverd[3026]: 2023-11-29T11:31:07.373+0100 [ERROR] agent.http: Request error: method=GET url=/v1/agent/self from=127.0.0.1:36206 error="Permission denied"
Nov 29 11:31:07 carbonio prometheus[929]: ts=2023-11-29T10:31:07.374Z caller=consul.go:295 level=error component="discovery manager scrape" discovery=consul config=advanced-auth msg="Error retrieving datacenter name" err="Unexpected response code: 403 (Permission denied)"

Anyone knows about them?

Thanks


   
ReplyQuote