Karma -Good speech by Jaggi Vasudev

Squid Proxy error ” TAG_NONE/503 0 CONNECT www.bing.com:443 – HIER_NONE/- -“

Error: When you try to browse internet through squid, the webpage will not be shown. But you can able to access squid server and port without any issues.

When you check in the access log on squid you will get an error ” TAG_NONE/503 0 CONNECT http://www.bing.com:443 – HIER_NONE/- -”  when I access bing.com.


Solution: Try to add the following line in /etc/squid/squid.conf

forward_max_tries 25 

This solves the issue for me.

Source url: https://www.vivaolinux.com.br/topico/Squid-Iptables/problema-squid3-para-baixar-anexos-do-outlook?pagina=02


Ubuntu apache2[10961]: AH00534: apache2: Configuration error: More than one MPM loaded.

Error scenario: Apache service not working with the following error “Ubuntu apache2[10961]: AH00534: apache2: Configuration error: More than one MPM loaded.”

The following are the error message when I try to start apache service.

root@Ubuntu:/var/log/apache2# /etc/init.d/apache2 restart

[….] Restarting apache2 (via systemctl): apache2.serviceJob for apache2.service failed because the control process exited with error code. See “systemctl status apache2.service” and “journalctl -xe” for details.




Root cause: To check the issue, I run the Journalctl-xe for the error logs

root@Ubuntu:/var/log/apache2# journalctl |tail

Mar 07 15:08:10 Ubuntu apache2[10961]: AH00534: apache2: Configuration error: More than one MPM loaded.

Mar 07 15:08:10 Ubuntu apache2[10961]: Action ‘configtest’ failed.

Mar 07 15:08:10 Ubuntu apache2[10961]: The Apache error log may have more information.

Mar 07 15:08:10 Ubuntu systemd[1]: apache2.service: Control process exited, code=exited status=1

Mar 07 15:08:10 Ubuntu systemd[1]: Failed to start LSB: Apache2 web server.

Mar 07 15:08:10 Ubuntu systemd[1]: apache2.service: Unit entered failed state.

Mar 07 15:08:10 Ubuntu systemd[1]: apache2.service: Failed with result ‘exit-code’.

Mar 07 15:09:01 Ubuntu CRON[10994]: pam_unix(cron:session): session opened for user root by (uid=0)

Mar 07 15:09:01 Ubuntu CRON[10995]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)

Mar 07 15:09:02 Ubuntu CRON[10994]: pam_unix(cron:session): session closed for user root


###### The bold highlighted is the cause where there is configuration issue in Apache. Hence I tried to check the configuration check command in Apache.######

root@Ubuntu:/var/log/apache2# apache2ctl -t

AH00534: apache2: Configuration error: More than one MPM loaded.

Action ‘-t’ failed.

The Apache error log may have more information.



Solution: Run the command a2dismod worker 

root@Ubuntu:/var/log/apache2# a2dismod worker

Module worker disabled.

To activate the new configuration, you need to run:

service apache2 restart

root@Ubuntu:/var/log/apache2# systemctl restart apache2.service

root@Ubuntu:/var/log/apache2# apache2ctl -t

Syntax OK



An internal error occurred – RDP

Error Message : An internal error occurred – RDP






Solution :

If you receive Event ID 1057 – “The Terminal Server has failed to create a new self signed certificate to be used for Terminal Server authentication on SSL connections. The relevant status code was Key not valid for use in specified state” from source TerminalServices-RemoteConnectionManager in the System event log, you may have an issue with a lot of strange advice. For me, none of which worked. I finally figured out the problem.

The conditions you’ll probably also notice is that you can’t remote desktop into the server until you remove the “Allow connection only from computers running Remote Desktop with Network Level Authentication” checkbox in the Remote Desktop Session Host Configuration’s RDP-Tcp properties General Tab or from the System settings under the Remote tab by changing the radio button back to “Allow connections from computers running any version of Remote Desktop (less secure)”.

In my case I had already tried a lot of the advice like deleting the self-signed certificate and rebooting (MMC/Certificates/Local Computer/Remote Desktop) And deleting these keys and restarting:
“HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM”  > Certificate “HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM” > CertificateOld “HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations” > SelfSignedCertificate

I also deleted the Host Configuration’s RDP-Tcp connection object all together and restarted the Remote Desktop Services service.

What did finally work, I noticed that we had a bunch of crypto keys that looked like this:

I moved them all to a subfolder so there were none left in the MachineKeys folder. I then opened the MachineKeys and re-applied the full-control permission to the local server administrators group. (Security/Advanced/Change Permissions/Replace all child object permissions) and applied this.

I then restarted the Remote Desktop Services service and this time I didn’t get the error about the certificate. I changed the security setting for RDP back to secure and was able to log on through Remote Desktop.

Url : https://blogs.technet.microsoft.com/the_9z_by_chris_davis/2014/02/20/event-id-1057-the-terminal-server-has-failed-to-create-a-new-self-signed-certificate/

Find SQL Server Instances Across Your Network Using Windows PowerShell


As more and more SQL Server instances get installed in my organization by different departments in both servers and desktops, I need to find out where they are as I’ll be responsible for managing and administering these instances. How do I list out all the SQL Server instances across my entire organization without even knowing where they are?


You may have probably heard about the term SQL Server sprawl – the uncontrolled and uncoordinated deployment of different SQL Server instances of different editions. It’s easy to track Enterprise and Standard Edition instances since we regularly do audits for licensing purposes. But, then, there are third-party and line-of-business applications that use SQL Server Express as their backend database that get installed by people from different departments of your organization. Who knows whether these SQL Server instances sit on their desktops or on servers allocated by the IT department? And the worst part is, we DBAs get charged for administering them.

You may have used tools like SQL Ping and a bunch of other stuff in the past, some of which are highlighted in this SQL Server Central article, to discover SQL Server instances in your network. The good news is, your nightmare is about to end. Since Windows PowerShell runs on top of the .NET Framework, it can leverage any .NET Framework-based assemblies available on the machine that it is running on top of (this includes having SQL Server 2005 Client Tools with Server Management Object (SMO) to administer SQL Server instances). For this particular case, you don’t even need to have SMO installed on your client machine to enumerate SQL Server instances across your organization as the .NET Framework already includes ADO.NET 2.0. ADO.NET contains the System.Data.Sql namespace which contains classes that support SQL Server-specific functionality. One of these classes is the SqlDataSourceEnumerator which can be used for enumerating all available instances of SQL Server within your local network, even if the SQL Server service is stopped. The SqlDataSourceEnumerator class has the Instance property that gets an instance of the SqlDataSourceEnumerator, which can then be used to retrieve information about available SQL Server instances. A method called GetDataSources retrieves a DataTable containing information about all visible SQL Server instances in the network from SQL Server 2000 onwards.

And this really highlights the power and simplicity of Windows PowerShell. This task can be done in a single line of code, using the information mentioned above.


Command : [System.Data.Sql.SqlDataSourceEnumerator]::Instance.GetDataSources()

Example :

PS C:\Users\vkarthikeyana> [System.Data.Sql.SqlDataSourceEnumerator]::Instance.GetDataSources()

ServerName        InstanceName         IsClustered              Version
———-             ————               ———–                 ——-
IN001VS0098      CONFIGMGRSEC           No                     11.0.6020.0
IN001VM0009     CITRIX_METAFRAME     No                     10.0.2531.0
IN001VS0012      CITRIX_METAFRAME     No                      10.0.2531.0
IN001VS0025      CITRIX_METAFRAME     No                      10.0.2531.0
IN001VM0023     AUTODESKVAULT         No                       12.0.2000.8
IN001VS0032       INSQL139                     No                       10.50.4000.0
IN001VS0023      CITRIX_METAFRAME      No                     10.0.2531.0





I have copied the above data for document purpose.


Source url: https://www.mssqltips.com/sqlservertip/2013/find-sql-server-instances-across-your-network-using-windows-powershell/


Another tool : https://www.idera.com/productssolutions/freetools/sql-instance-check

which does the same job and in this site lot of free tools available.




Blank default gateway may occur after configuring Static IP address

Error: Blank default gateway may occur after configuring Static IP address or if you configure IP address in your NIC by next restart of VM or the guest OS the gateway will disappear.

Cause:  When removing a network driver using a vendor-provided uninstallation program or through Device Manager, previously entered static IP address information may not be removed correctly from the registry. After reinstalling the network driver and reentering the same static IP address, the presence of previous registry information prevents the newly entered address information from being saved correctly.

For VM if you upgrade VMtools or any hardware version this error will occur to some of the VM.


Open a command prompt under the administrator context and run the following command TWICE, using the desired static address information. For example:

netsh interface ipv4 set address “Local Area Connection” static

Note: This first command may return an error “Object already exists”
netsh interface ipv4 set address “Local Area Connection” static


Note: This command should succeed with no errors

To Find iDRAC IP Address on ESX Host

Scenario : To identify iDRAC IP address of ESXi host through cli. This would be useful when you forget the IP Address of idrac.



There is no VMware command to find the IP address of iDRAC. But we can get the information from local CIM providers through ESXi shell query.


# enum_instances OMC_IPMIIPProtocolEndpoint root/cimv2 | grep IPv4Address

IPv4Address =