59 reputation
6
bio website
location
age
visits member for 1 year, 5 months
seen Apr 2 at 1:24
stats profile views 5

Apr
2
comment How to suppress an unwanted external Autodiscover lookup?
Did you add that to the external DNS?
Jan
3
comment How to suppress an unwanted external Autodiscover lookup?
The first command has the 2 fields blank. The second has just the InternalUrl, which points to mx.externaldomain.com/ews/exchange.asmx
Jan
2
comment How to suppress an unwanted external Autodiscover lookup?
It's 2007. I can run the 2 commands but the results are too large to be posted here. Anything in particular? I don't see any reference to cpanel.net or any other outside domains.
Dec
31
comment How to suppress an unwanted external Autodiscover lookup?
It's not a hosted exchange, I have full control over it. The test above fails everything (no autodiscover found), except for the DNS name resolution which is correct.
Dec
27
comment How to suppress an unwanted external Autodiscover lookup?
It lists the correct 3 MX adresses we use. Nothing pointing to cpanel.net.
Jul
10
comment Puppet Agent still able to connect to Master after certificate revocation
Apache was on the server before installing puppetmaster, but I haven't modified the puppetmaster installation by any means. I frankly don't know what to answer. Can I check this somehow?
Jul
9
comment Puppet Agent still able to connect to Master after certificate revocation
No, the file doesn't even exist.
Jun
21
comment Puppet Agent still able to connect to Master after certificate revocation
(1) puppetd --onetime --no-daemonize --verbose --waitforcert 5 (2) --test runs properly, even when the cert has been revoked (3) Unfortunately I've never been able to enable logging on the master...
Jun
21
comment Puppet Agent still able to connect to Master after certificate revocation
(1) I don't have a new client to try the -c, but it's the usual success message. (2) -l lists the certs and it's not there anymore. (3) Ubuntu 10.04, puppet 2.7.9 (4) Do you mean service puppetmaster start? (5) 12 clients
Mar
7
comment Puppet: Could not find init script for 'squid'
Right for Debian, but still nothing in Ubuntu. I switched to upstart which solved it. Thanks for your help!
Mar
7
comment Puppet: Could not find init script for 'squid'
Stupid me... after the puppet upgrade I forgot to add provider => 'upstart',... works like a charm! Thanks!
Mar
7
comment Puppet: Could not find init script for 'squid'
Upgraded to Puppet 2.7.11 and still same result. Damn it...
Mar
7
comment Puppet: Could not find init script for 'squid'
I redid the machine from scratch and the same problem applies. Let me try to upgrade Puppet to see if it makes a difference...
Mar
7
comment Puppet: Could not find init script for 'squid'
I can't see the symlink in that directory and I get Invalid service provider 'upstart' from puppet. However, squid is up and running...
Mar
7
comment Puppet: Could not find init script for 'squid'
returns nothing. As a double check, on a working machine it returns /etc/init.d/squid
Mar
6
comment Puppet: Could not find init script for 'squid'
service squid start/stop. I used apt-get install squid.
Mar
6
comment Puppet: Could not find init script for 'squid'
Squid is installed and already running.
Mar
6
comment Puppet: Could not find init script for 'squid'
How can I find the correct name?
Mar
6
comment Puppet: Could not find init script for 'squid'
I can't find anything related to squid there...
Mar
6
comment Puppet: Could not find init script for 'squid'
I'm using Squid 2.7.STABLE9 though.