Friday, June 11, 2021

Recent Questions - Server Fault

Recent Questions - Server Fault


Delete all folders on all drives with "foo" OR "bar" in the folder name with batchfile

Posted: 11 Jun 2021 11:40 AM PDT

I am trying to delete all folders on all drives with the above naming pattern, however only on the first folder level, i.e directly below the drive letter, like for example:

F:\this folder's name contains FOO and should be deleted  

...without confirmation nor error message (e.g. in case no folders are found), with a batchfile.

I've found this: delete all folders with tmp in name using batch file and am wondering if the solution from there is a good starting point?

@echo off  set dir="c:\FOLDERLOCATION\"  FOR /D /R %dir% %%X IN (*.tmp) DO RMDIR /S /Q "%%X"  pause  exit  

How do I prevent docker from exiting when my app crashes

Posted: 11 Jun 2021 11:35 AM PDT

I need to debug an application that is crashing inside a docker, how do I achieve that the docker does not stop when the app crashes, allowing me to -it inside and try starting the app manually?

ls command that shows AM/PM

Posted: 11 Jun 2021 11:26 AM PDT

I'm using a CentOS 7 OS, configured based on AM/PM. Is there a linux command line (like ls --full-time) that shows full time information including AM/PM?

Below example does not show AM/PM:

# ls --full-time  # -rw-------. 1 root root 125274133976 2021-06-10 05:43:58.348897593 -0700 file1.tar.gz  # -rw-------. 1 root root 187085036220 2021-06-10 08:28:56.257324419 -0700 file2.tar.gz  

Unexplained Network Activity to messenger.hotmail.com

Posted: 11 Jun 2021 11:31 AM PDT

I am seeing thousands of network requests per second to messenger.hotmail.com from my Windows 10 machine. I first noticed it due to the high number of DNS requests for the domain and then using Sysinternals Process Monitor I was able to see multiple applications sending and receiving requests to the domain. The operations (TCP Receive/TCP Send) are using multiple ports. FireFox seems to generate the bulk of the requests. I am including some examples below.

  • firefox.exe - messenger.hotmail.com:51380 -> messenger.hotmail.com:51381
  • Code42Service.exe - messenger.hotmail.com:52106 -> messenger.hotmail.com:4244
  • OVRServer_x64.exe (Oculus) - messenger.hotmail.com:58723 -> messenger.hotmail.com:58724

What I have tried:

  • I tried blocking the domain in the Hosts file by setting the IP for the domain to 127.0.0.1 (I also tried a nonexistant LAN address) to see if it would break anything but this didn't seem to have any effect.
  • I turned off all plugins in Firefox to see if it might have been caused by a plugin, no effect.

My system:

  • Windows 10 Pro Version 1909, Build 18363.1500
  • 64 -bit Intel Core i7

Any ideas on why this might be happening? Should I try blocking this in the firewall? On a related note I couldn't figure out why the DNS wasn't being cached which is how I first noticed it.

Let openldap users change password with passwd in centos, i broke it

Posted: 11 Jun 2021 10:48 AM PDT

Tried to do the above with this tutorial:

https://www.unixguide.net/content/openldap-allow-users-change-their-password-unix-passwd-command

So I created this ldif:

dn: olcDatabase={2}hdb,cn=config  changetype: modify  add: olcAccess  olcAccess: to attrs=userPassword by self write by anonymous auth by dn.base="cn=ldapadm,dc=bbb,dc=local" write by * none    add: olcAccess  olcAccess: to * by self write by dn.base="cn=ldapadm,dc=bbb,dc=local" write by * read  

Ran the ldapmodify, now no user can log into any client with their password when they could before I ran the above modify.

now attempting to login says permission denied after correct password is entered....what did I break ?? (totally new to openldap)

And as it might be relevant this is how I got my clients connected to my openldap server:

yum install -y openldap-clients nss-pam-ldapd  authconfig --enableldap --enableldapauth --ldapserver=192.168.1.10 --ldapbasedn="dc=bbb,dc=local" --enablemkhomedir --update  

Contact WebRelay behind cellular modem

Posted: 11 Jun 2021 10:18 AM PDT

We are trying to open a gate at a remote client site from our server. We were wanting to get this relay (WebRelay) set up behind a cellular modem. The issue is that I can no longer contact the relay from the typical ipv4 that I would normally have access to on a wired connection.

This is an issue outside my skill-set. My assumption is that I will have to connect the modem to a vpn and access the relay that way. I was looking at the AirLink RV50 from Sierra Wireless as it has an interface for VPN Gateways.

All I need to do is to be able to send a single packet telling it to open. Is there a simpler way to do this? I have never done anything like this but since this is a small company, I am the one that has to.

Thanks!

Creating a LoggingServiceV2Client with custom credentials

Posted: 11 Jun 2021 10:03 AM PDT

I've been working on a C# desktop app that should be able to connect to a GCP account and pull/query the Logs there. I want this to be usable on computer, or to be able to access different accounts, so I don't want to rely on the Private key stored on the machine. Instead, I'm going to pass in an access token manually. This means that I cannot use the default "LoggingServiceV2Client.Create()" route to build the client. Instead, I'll need to use the "LoggingServiceV2ClientBuilder" class. However, I am having a lot of trouble setting the client up correctly, and have yet to get it to return a single successful query.

What I am using so far is:

           string cc = "super secret access token";                var cred = GoogleCredential.FromAccessToken(cc);                cred = cred.CreateScoped(LoggingServiceV2Client.DefaultScopes);                  var client = new LoggingServiceV2ClientBuilder { ChannelCredentials = cred.ToChannelCredentials()}.Build();  

Trying to get sudoers working on openldap/centos7

Posted: 11 Jun 2021 09:59 AM PDT

I was following this tutorial here:

https://kifarunix.com/how-to-configure-sudo-via-openldap-server/

A lot of it made sense, but still new to openldap so some of this is cryptic too. I have the openldap running with users authenticating on other machines even working with phpldapadmin. So it was time to get sudoers working for some users. I ran the sudoers2ldif command and got a file similar to what was showed in the tutorial, and edited it accordingly. When It came time to run ldapadd -Y EXTERNAL -H ldapi:/// -f sudoers_modified.ldif it failed with the error:

SASL/EXTERNAL authentication started  SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth  SASL SSF: 0  adding new entry "cn=defaults,ou=SUDOers,dc=apo,dc=local"  ldap_add: Invalid syntax (21)      additional info: objectClass: value #1 invalid per syntax  

Is the 21, the line number of the .ldif file? Or some other error code...also no idea what is invalid on the objectClass command... posted is the ldif file below.

dn: cn=defaults,ou=SUDOers,dc=bbb,dc=local  objectClass: top  objectClass: sudoRole  cn: defaults  description: Default sudoOption's go here  sudoOption: !visiblepw  sudoOption: always_set_home  sudoOption: match_group_by_gid  sudoOption: always_query_group_plugin  sudoOption: env_reset  sudoOption: env_keep =  "COLORS DISPLAY HOSTNAME HISTSIZE KDEDIR LS_COLORS"  sudoOption: env_keep += "MAIL PS1 PS2 QTDIR USERNAME LANG LC_ADDRESS LC_CTYPE"  sudoOption: env_keep += "LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES"  sudoOption: env_keep += "LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE"  sudoOption: env_keep += "LC_TIME LC_ALL LANGUAGE LINGUAS _XKB_CHARSET XAUTHORITY"  sudoOption: secure_path = /sbin:/bin:/usr/sbin:/usr/bin    dn: cn=sudo,OU=SUDOers,dc=bbb,dc=local  objectClass: top  objectClass: sudoRole  cn: sudo  sudoUser: bobby  sudoHost: ALL  sudoRunAsUser: ALL  sudoCommand: ALL  

Maybe sudoRole needs to be added somehow? The other ldif I added successfully for this was:

dn: ou=SUDOers,dc=bbb,dc=local  objectCLass: top  objectClass: organizationalUnit  ou: SUDOers  description: BBB SUDOers container  

I had found another tutorial here:

https://forums.centos.org/viewtopic.php?t=73807

With similar information slightly different, I didn't use this one because one of the ldif files that was posted had a ton of stuff that said it was 'autogenerated' and I had no idea how or where it came from.

(the vi /testfolder/sudoers.ldif in the post)

Do I need to set a MX record with both my domain registrar & hosting?

Posted: 11 Jun 2021 10:28 AM PDT

I have a GoDaddy registered domain and am using the GoDaddy O365 email.

I am moving to a different host for my website, so I have changed the A record in GoDaddy's settings to point to my shared hosting IP. The nameservers are still set to GoDaddys, with all the original settings for e-mail still there too (SPF, MX records, etc)

E-mail still works, as well as the website, but whenever I try to send an e-mail out from my shared hosting (a wordpress site), the e-mail is never received to e-mails *@mydomain.com. But they are received to others, such as gmail or hotmail, but often end up in junk.

When I use an e-mail tester, I get a bunch of errors about MX record missing, SPF not authenticated, etc.

What I am worried about is, when creating this shared hosting account ( in WHM ), I did not check the box for "use dns settings from domain registrar". So now on my shared hosting account there is a DNS section with a bunch of records in it for this domain.

Should I try deleting all the records from within my hosting, so it reverts to using everything from my registrars DNS for e-mail?

Connecting Computers accross different subnets or IP addresses

Posted: 11 Jun 2021 10:29 AM PDT

I have a setup that involves:

  • Cable modem/router at 192.168.10.1
  • Wireless Router 1 at 192.168.20.1
  • Wireless Router 2 at 192.168.30.1

The wireless router are connected to the Cable Modem via the WAN port. Singly they work great, but the problem occurs when trying to access a computer or resource that is located under a different router from another.

For an example, a computer connected on Wireless Router 1 can not access a computer connected on Wireless Router 2 or a Computer connected directly to the cable modem.

I want the IPs from 192.168.10.1 and 192.168.20.1 and 192.168.30.1 to all talk to each other.

I have read several posts and I think it has something to do with the routing table. Unfortunately, I tried many settings, and nothing seems to work.

I did not try any routing table modification on the cable modem as yet.

Please see my picture below as it has all of the settings I have set and will illustrate my issue better.

Here is the picture of the Network Setup and setting from the router

Thanks for your help.

xfs superblock corrupted after power cut

Posted: 11 Jun 2021 09:24 AM PDT

Like others before me the superbock on my xfs drive has become corrupted. I've tried xfs_repair and xfs_repair -L to restore the drive but both report back the same result:

Phase 1 - find and verify superblock...  superblock read failed, offset 0, size 524288, ag 0, rval -1    fatal error -- Input/output error  

{mkfs.xfs -Nf /dev/sdb1} reports back the following:

meta-data=/dev/sdb1              isize=512    agcount=4, agsize=244188544 blks           =                       sectsz=4096  attr=2, projid32bit=1           =                       crc=1        finobt=1, sparse=1, rmapbt=0           =                       reflink=1  data     =                       bsize=4096   blocks=976754176, imaxpct=5           =                       sunit=0      swidth=0 blks  naming   =version 2              bsize=4096   ascii-ci=0, ftype=1  log      =internal log           bsize=4096   blocks=476930, version=2           =                       sectsz=4096  sunit=1 blks, lazy-count=1  realtime =none                   extsz=4096   blocks=0, rtextents=0  

Having followed various posts on this subject which all say siliar things to what I've tried above I have the sinking feeling the drive contents is lost (Thanks EDF Energy). Does anyone have any further recovery suggestions?

How to proxy IMAP/POP3 connection to appropriate backend mail server by domain

Posted: 11 Jun 2021 09:00 AM PDT

I have system with multiple email server (exchange, zimbra) for multiple domain. So when users of domain A want connect to server for getting email they have to use IP of server A (Ex: 192.168.10.253), same way with user of domain B, they have to use IP of server B (Ex: 192.168.20.253).

I want simplify connection between users and mail server by create a proxy server for IMAP/POP3 connection but I can not find solution to do it, is there anyway to do it? pls give me the keywork or a solution for better. Thank you so much.

Image description for my question

Wordpress on IIS crashes intermittently

Posted: 11 Jun 2021 08:49 AM PDT

My wordpress site running on IIS has been crashing every once in a while with "There has been a critical error on your website" If I restart IIS or the AppPool, it starts working again. It's a pretty basic wordpress site, just a few basic plugins

When I look at the php error log I find this:

[11-Jun-2021 05:05:56 UTC] PHP Warning:  require_once(C:\inetpub\wwwroot\wp-includes\s): failed to open stream: No such file or directory in C:\inetpub\wwwroot\wp-includes\sodium_compat\autoload.php on line 40  [11-Jun-2021 05:05:56 UTC] PHP Fatal error:  require_once(): Failed opening required 'C:\inetpub\wwwroot\wp-includes\sodium_compat/src/SodiumException.php' (include_path='.;C:\php\pear') in C:\inetpub\wwwroot\wp-includes\sodium_compat\autoload.php on line 40  

It says it fails opening the file, but the file does exist, and I can open it. I thought the different slashes in the filename might be the problem, but I can copy and past that exact path into the Run prompt and it opens fine.

At the time of the problem, available memory seems fine, and not noticing any traffic spikes.

Windows Server 2019 datacenter IIS 10.0 MySql 5.7.31 Wordpress 5.5.5 Php 7.3.13

What troubleshooting steps would you recommed?

HDD with SSD Cache to RAID6?

Posted: 11 Jun 2021 09:56 AM PDT

We got 8 HDDs in our server (Dell PowerEdge R730), combined as a RAID6 array. Yesterday evening one of the drives failed, so we are looking now for a replacement.

I've found the Seagate Exos E 10E2400 which got a 256 MB Cache and a 16 GB SSD Cache. Currently, installed are HGST Ultrastar C10K1200 with only a 64 MB cache and no SSD cache.

Would this be a problem to mix them?

Determine the full oslevel (incl build date) of a local AIX repository without patching / installing

Posted: 11 Jun 2021 09:03 AM PDT

In our environment only 1 of our AIX servers is permitted to access the internet through the firewall. On this 1 server I use suma to download all fixes for all base levels, technology levels and service packs that we have in our environment (this is done daily). Once a month I copy all fixes together in 1 folder per base level and I use inutoc to create a couple "repositories" that are frozen and that can be used to patch all of our AIX servers (this way we can ensure all servers are on the same oslevel). We call this a "monthly patchset".

We have a csv file that lists all kernel versions for each "monthly patchset" for all of our UNIX/Linux OS flavors. That csv file is used by our patching / validation scripts. For Linux / Solaris I've found "tricks" to determine the kernel version from the repository files themselves. But on AIX I'm failing to figure out the oslevel without actually patching a server with it. After patching, I can run 'oslevel -s' to figure the oslevel, but that is too late, as our patching scripts use / require the oslevel before starting the actual patching...

So does anyone know a trick to accomplish this? I've tried the following so far:

  • Our repository folder contains many *.bff files, which are binary files, so inside those files I can't find the oslevel
  • The*.bff file names are mostly 'U' followed by some numbers and '.bff' (so not usuable for determining the oslevel). But some filenames actually do contain (parts of) the oslevel in the filename. For example: 7200-01-06.bff 7200-02-01-1732.bff 7200-02-06.bff 7200-03-06.bff 7200-03.bff 7200-04-01.bff 7200-04-02.bff 7200-04-03.bff 7200-04.bff 7200-05-01.bff 7200-05-02.bff 7200-05.bff. However, as you can see, from the latest oslevels, the 'build date' part is missing in the filename.
  • We patch using the "install_all_updates -Y -d <path_to_repo>" command. I've tried using "install_all_updates -p -d <path_to_repo>", hoping that it would be visible somewhere in the output, but it isn't...
  • I've also tried "installp -[lL] -d <path_to_repo>", but also there the oslevel isn't visible...

I hope someone can assist me with this. Thanks in Advance!

Google Cloud BigQuery Analytic Support

Posted: 11 Jun 2021 08:39 AM PDT

I am trying to query the event_params.key and event_params.value for my analytic dataset but I am unclear as to the syntax to use as the event_params is a dictionary. Currently i am getting an error cannot access field on a value with type array<struct.

Any help will be greatly appreciated.

D

remotely installing python and pip packages

Posted: 11 Jun 2021 08:46 AM PDT

I'm trying to install python with pip packages remotely on an Azure VM using powershell. The script deployed to the VM:

Start-Process 'F:\python-3.9.5-amd64.exe'-ArgumentList ("/passive", "InstallAllUsers=1", "PrependPath=1", "Include_test=0", "Include_pip=1") -Wait  Start-Sleep -s 120  & pip install urllib3 --no-index --find-links 'F:\urllib3-1.26.5-py2.py3-none-any.whl'  & pip install selenium --no-index --find-links 'F:\selenium-3.141.0-py2.py3-none-any.whl'  

Python is installed correctly in Program Files, and environment variables are added, but pip is not recognised.

I've tried setting an environment variable in the script (set / setx ..) for both the Python and the Scripts folders, but it didn't help. If I RDP on to the machine pip is recognised, and the packages are installed correctly. python is not recognised either (tried python -m pip install ...).

Why is pip not recognised?

load balance for kubernetes master on different subnet

Posted: 11 Jun 2021 08:38 AM PDT

I'm trying to build an architecture for new k8s cluster with master HA on different sites (different subnets).

The issue I'm facing is finding an open source Software Load Balance (there is no physical on the site, and its an on prem env) who can support different subnets (GSLB).

The Load balancer is for the Apiserver and all connectivity to the masters.

Those anyone deploy that architecture? witch LB did you use? I cant use HAproxy or seesaw bc they dont support different subnets.

Why can't Openshift cannot access metrics API but metrics is setup?

Posted: 11 Jun 2021 10:57 AM PDT

I am trying to get autoscaling working on openshift OKD. I am using Openshift 3.11.

So I have installed metrics and Hawkular metrics and set the url's and set the host files to point to it.

Getting the HorizontalPodAutoscaler:

oc describe hpa  

Gives:

Name:                                                  blog  Namespace:                                             demo  Labels:                                                <none>  Annotations:                                           <none>  CreationTimestamp:                                     Mon, 28 Oct 2019 13:35:07 +0200  Reference:                                             DeploymentConfig/blog  Metrics:                                               ( current / target )    resource cpu on pods  (as a percentage of request):  <unknown> / 50%  Min replicas:                                          1  Max replicas:                                          10  DeploymentConfig pods:                                 3 current / 0 desired  Conditions:    Type           Status  Reason                   Message    ----           ------  ------                   -------    AbleToScale    True    SucceededGetScale        the HPA controller was able to get the target's current scale    ScalingActive  False   FailedGetResourceMetric  the HPA was unable to compute the replica count: unable to get metrics for resource cpu: unable to fetch metrics from resource metrics API: the server could not find the requested resource (get pods.metrics.k8s.io)  Events:    Type     Reason                        Age                From                       Message    ----     ------                        ----               ----                       -------    Warning  FailedComputeMetricsReplicas  1h (x41 over 1h)   horizontal-pod-autoscaler  failed to get cpu utilization: unable to get metrics for resource cpu: unable to fetch metrics from resource metrics API: the server could not find the requested resource (get pods.metrics.k8s.io)    Warning  FailedGetResourceMetric       4m (x171 over 1h)  horizontal-pod-autoscaler  unable to get metrics for resource cpu: unable to fetch metrics from resource metrics API: the server could not find the requested resource (get pods.metrics.k8s.io)  

So it cannot access the Metrics API.

Furthermore getting the metricsAPIProxy gives:

oc adm diagnostics MetricsApiProxy  

Gives:

[Note] Determining if client configuration exists for client/cluster diagnostics  Info:  Successfully read a client config file at '/Users/example/.kube/config'  Info:  Using context for cluster-admin access: 'demo/openshift-example-co-za:8443/exampleh'    [Note] Running diagnostic: MetricsApiProxy         Description: Check the integrated heapster metrics can be reached via the API proxy    ERROR: [DClu4003 from diagnostic MetricsApiProxy@openshift/origin/pkg/oc/cli/admin/diagnostics/diagnostics/cluster/metrics.go:89]         Unable to access the metrics API Proxy endpoint /api/v1/proxy/namespaces/openshift-infra/services/https:heapster:/api/v1/model/metrics:         (*errors.StatusError) the server could not find the requested resource         The Horizontal Pod Autoscaler is not able to retrieve metrics to drive scaling.    [Note] Summary of diagnostics execution (version v3.11.0+0cbc58b):  [Note] Errors seen: 1  

Docker Compose WordPress, where are my WordPress files stored

Posted: 11 Jun 2021 10:27 AM PDT

I have successfully setup WordPress following the official instructions on docker's documentation. I am running windows and I can't seem to figure out where I edit my WordPress files such as wp-content so on so fourth. Here is my docker-compose.yml that I used to setup the container. Thanks ahead of time. Does it have something to do with the volumes setting? I shared my C drive with docker.

version: '3.3'    services:     db:       image: mysql:5.7       volumes:         - db_data:/var/lib/mysql       restart: always       environment:         MYSQL_ROOT_PASSWORD: somewordpress         MYSQL_DATABASE: wordpress         MYSQL_USER: wordpress         MYSQL_PASSWORD: wordpress       wordpress:       depends_on:         - db       image: wordpress:latest       ports:         - "8080:80"       restart: always       environment:         WORDPRESS_DB_HOST: db:3306         WORDPRESS_DB_USER: wordpress         WORDPRESS_DB_PASSWORD: wordpress  volumes:      db_data: {}  

Edit: I would like to have my WordPress files in the same directory that I setup the container which is C:/Users/andersk/sites/wordpress.

IIS ARR ReverseProxy with Client Certificate Authentication for backend IIS

Posted: 11 Jun 2021 09:05 AM PDT

We have legacy SOAP Web Services (https://dev-ms01/Services/default.asmx) which are written in asp.net 1.1 hosted on IIS7(win server 2008 standard),web services consumed by clients by providing Client Certificate. For the SSL Certificates settings we have Accept on this IIS

`Client(Request with SSL Client Certificate)--> IIS7 (on host dev-ms01)--> Asp.Net SOAP WebServices`  

Now I'm trying to set up proxy IIS(IIS10 on win server 2016 64bit host secure-dev-ms01) with revere proxy for the IIS7. I've followed msdn article https://blogs.msdn.microsoft.com/friis/2016/08/25/setup-iis-with-url-rewrite-as-a-reverse-proxy-for-real-world-apps/ to configure URL rewrite with ReverseProxy as below

`Client(Request with SSL Client Certificate)--> Proxy IIS10 Server with ReverseProxy (on host secure-dev-ms01)--> IIS7 (on host dev-ms01) --> Asp.Net SOAP WebServices`  

On the IIS10(host secure-dev-ms01) for the SSL Certificates settings I've chosen Accept and I've tried the below ReverseProxy configuration enter image description here. When I'm trying to browse the proxy web services URL as https://secure-dev-ms01/Services/default.asmx it is prompting the client certificate but after providing the client certificate am seeing below error

403 - Forbidden: Access is denied.  You do not have permission to view this directory or page using the credentials that you supplied.  

I've tried using below RevereProxy as wellenter image description here and tried browsing the proxy web services URL https://secure-dev-ms01/Services/default.asmx and provided the client certificate but still am seeing below error. I've also tried unchecking the option Enable SSL Offloading for both of the above RevereseProxy configurations, but that didnt work either

403 - Forbidden: Access is denied.  You do not have permission to view this directory or page using the credentials that you supplied.  

I found this msdn article https://blogs.msdn.microsoft.com/asiatech/2014/01/27/configuring-arr-with-client-certificate/ which suggests changingSSL Certificates settings to Ignore on the backend server(but we can not adopt this for our organization) and try using the certificate from the headers X-ARR-ClientCert but we are trying to avoid making any code changes to the legacy asp.net 1.1 services

I couldnt find any relevant articles that could make IIS ARR ReverseProxy with Client Certificate Authentication work for backend IIS with just configuration tweaks on the IIS10 with ReverseProxy instead of code/config change on the backend IIS7, can someone please help me to make this work?

Kernel update not being applied even after reboot

Posted: 11 Jun 2021 10:02 AM PDT

Here is my server details

cat /etc/*-release  CentOS Linux release 7.3.1611 (Core)  NAME="CentOS Linux"  VERSION="7 (Core)"  ID="centos"  ID_LIKE="rhel fedora"  VERSION_ID="7"  PRETTY_NAME="CentOS Linux 7 (Core)"  ANSI_COLOR="0;31"  CPE_NAME="cpe:/o:centos:centos:7"  HOME_URL="https://www.centos.org/"  BUG_REPORT_URL="https://bugs.centos.org/"    CENTOS_MANTISBT_PROJECT="CentOS-7"  CENTOS_MANTISBT_PROJECT_VERSION="7"  REDHAT_SUPPORT_PRODUCT="centos"  REDHAT_SUPPORT_PRODUCT_VERSION="7"    CentOS Linux release 7.3.1611 (Core)  CentOS Linux release 7.3.1611 (Core)  

I wanted to update Kernel to latest version in order to run docker

I did update using yum update and showed me that its updating kernel to some 4.* version.

Then I did reboot

And then I saw

[root@vps ~]# uname -r  2.6.32-042stab116.2  

Its still running older version.

I tried solution from https://serverfault.com/a/623755/213444

But my server has no such files at those locations.

What is going wrong?

SMTP load balancing with remote host's IP passed through to SMTP servers?

Posted: 11 Jun 2021 09:05 AM PDT

I'm attempting to build a load-balanced SMTP cluster. The mail servers already exist and run Exim 4. Initially, I looked at using Nginx to do the load-balancing, however on the test system all the mail servers see the inbound connections as coming from the load-balancer IP rather than the actual remote sender IP, and after extensive Googling there doesn't appear to be any way round this. As that effectively turns the mail cluster into an open relay it's clearly a non-starter, which is a pity as Nginx works beautifully otherwise.

So I'm looking to use HAProxy instead, as I gather from further Googling that it has the ability to pass the connections with their original source IP intact so the system relay-allow lists and ACLs will operate correctly.

However having set HAProxy up as per several on-line examples, I either get "SMTP synchronisation error" (and a 500 series error so mail will bounce), and the connection immediately dropping, or just the connection dropping with no SMTP message at all.

Here is the haproxy.conf that's in use:

global        log         127.0.0.1 local2        chroot      /var/lib/haproxy      pidfile     /var/run/haproxy.pid      maxconn     4000      user        nobody      group       nobody      daemon        stats socket /var/lib/haproxy/stats    defaults      log                     global      option                  redispatch      retries                 3      timeout queue           1m      timeout connect         10s      timeout client          1m      timeout server          1m      timeout check           10s      maxconn                 3000    listen smtp      bind 0.0.0.0:25      mode tcp      no option http-server-close      balance roundrobin  #    option smtpchk HELO smtp-in.example.com      server smtp01 10.0.0.141:25 send-proxy check      server smtp02 10.0.0.143:25 send-proxy check  

Despite the presence of the send-proxy command, which I gather is how you tell haproxy to pass through the source IP, the Exim logs look like this:

016-12-26 07:06:48 SMTP protocol synchronization error (input sent without waiting for greeting): rejected connection from H=[10.0.0.150] input="PROXY TCP4 10.0.0.150 10.0.0.143 40334 25\r\nHELO smtp-in.example.comr\n"

In this case .150 is the load balancer and .143 is the Exim SMTP server.

Questions:

  1. Is it in fact possible to get Nginx to present the SMTP connections to the mail servers with the source IP being the real remote source IP instead of the load-balancer?

  2. Alternatively, is this possible in HAProxy, and how is it done?

In this case the current production system runs LVS, however that relies on both the load balancer and the loopback interfaces on all the mail servers sharing the same IP address. The new load balancer will be OpenSUSE 42.2, and amongst other things if that detects an IP already in use on the network it appears to helpfully removes it from itself to avoid a conflict. So LVS is out in the new build.

Other solutions to the problem which I'm considering include separating inbound and outbound SMTP traffic entirely (currently it all runs through the same load balancer), installing a simple relay (qmail possibly) on the load-balancer IP address, configured to only allow recognised ranges as per standard relay practice, and using simple DNS round-robin on the MX records to send inbound SMTP direct to the mail servers. But a load-balanced solution would be more elegant.

Why does VNC viewer on Mac Book Pro report RFB protocol error when connecting to AWS over L2TP?

Posted: 11 Jun 2021 10:26 AM PDT

There is a small group of us working on Amazon Web Services (AWS), we use mac books as our desktop machines and VNC into servers running on AWS. The problem started when we upgraded our VPN from PPTP to L2TP (Centos 6 with Openswan). My colleague who set it up had no problems with the new VPN. However, within a few minutes of connecting my VNC viewer sessions went dark and reported:

RFB Protocol Error: Bad hextile data or RFB Protocol Error: Bad xrle data

and other of the encoding protocols used by RFB (Remote Frame Buffer). This continued every minute or so depending on activity, with a delay while it corrected itself of up to 10 seconds. Clearly unusable. I went back to the PPTP VPN and continued without problem. Yesterday however, we connected another colleague to the L2TP VPN and he saw the same issues as me, so now we have to fix it.

The only discernible difference was that the two of us having problems with the VPN have mid-2014 15-inch Mac Book Pro with retina display (bought early 2015 with Yosemite) whereas my colleague that does not have this problem has a Mac Book Air (13-inch, Mid 2013) upgraded to Yosemite.

Searches for RFB protocol error have turned up nothing and other than that I don't even know what to search for or even ask about.

Any help appreciated.

unable to login remotely in MYSQL

Posted: 11 Jun 2021 11:01 AM PDT

I am very new to mysql and I want to use remote login I followed this stack process but the command gives me nothing on the screen as listed on that link

$ lsof -i -P | grep :3306  $  

this is the output.

What I did so far: I edited the file /etc/mysql/my.cnf to make change and looks like this

skip-external-locking  #  # Instead of skip-networking the default is now to listen only on  # localhost which is more compatible and is not less secure.  bind-address        = 0.0.0.0  

What I want basically that I want remote login.But I am unable to that. I run following command on my terminal

$ mysql -h 127.6.110.2 -u adminTwz5PWn -p  $ enter password:  ERROR 1045 (28000): Access denied for user 'adminTwz5PWn'@'localhost' (using password: YES)  

For sake of information needed I got this username and password from Openshift My concern is that how @'localhost' comes into the picture If I am providing the host ip in the command

I have user log in to mysql as follows

+------------------+---------------+  | user             | host          |  +------------------+---------------+  | root             | %             |  | root             | 127.0.0.1     |  | adminvKbP1kf     | 127.3.138.130 |  | adminTwz5PWn     | 127.6.110.2   |  | root             | ::1           |  | user             | hostname      |  | debian-sys-maint | localhost     |  | phpmyadmin       | localhost     |  | phpmyadmin_suraj | localhost     |  | root             | localhost     |  | suraj            | localhost     |  +------------------+---------------+  

Please correct me if I am wrong anywhere. And what steps are needed to make this successfull

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message

Posted: 11 Jun 2021 11:01 AM PDT

One of my server (Ubuntu 12.04, 16CPU, 32GB RAM) runs the app section of my website (Nginx 1.1.19, PHP5-FPM, Php 5.3.10, Symfony2 Web Framework)

Suddenly, users started getting HTTP 5** Errors. When I went on the server, there was huge disk IO and the culprit was [flush].

When I went through the kernel logs using dmesg, it showed the reason for [flush] was nginx processes taking too much time to flush. (I think)

Kernel Log entry from the time of Incident:

Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.048088] INFO: task nginx:17876 blocked for more than 120 seconds.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.050180] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057484] nginx           D ffffffff81806240     0 17876  17875 0x00000000  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057488]  ffff88075deeda68 0000000000000082 ffff88063383be38 ffff880427d450d0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057491]  ffff88075deedfd8 ffff88075deedfd8 ffff88075deedfd8 0000000000013700  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057494]  ffffffff81c0d020 ffff880734362de0 ffff88075deeda78 ffff88075deedad8  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057501] Call Trace:  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057508]  [<ffffffff8165badf>] schedule+0x3f/0x60  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057513]  [<ffffffff8126163d>] do_get_write_access+0x27d/0x4f0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057519]  [<ffffffff8108b920>] ? autoremove_wake_function+0x40/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057523]  [<ffffffff8129f1fe>] ? security_inode_alloc+0x1e/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057526]  [<ffffffff81261a00>] jbd2_journal_get_write_access+0x30/0x50  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057531]  [<ffffffff812439fe>] __ext4_journal_get_write_access+0x3e/0x80  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057536]  [<ffffffff8121453a>] ext4_new_inode+0x19a/0xb10  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057540]  [<ffffffff81220745>] ? ext4_lookup.part.27+0x75/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057543]  [<ffffffff81221e58>] ext4_create+0xb8/0x140  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057547]  [<ffffffff81185da4>] vfs_create+0xb4/0x120  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057551]  [<ffffffff81187a79>] do_last+0x5c9/0x730  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057554]  [<ffffffff81188f81>] path_openat+0xd1/0x3f0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057559]  [<ffffffff8152beea>] ? sock_poll+0x1a/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057563]  [<ffffffff811893c2>] do_filp_open+0x42/0xa0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057567]  [<ffffffff8131b481>] ? strncpy_from_user+0x31/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057570]  [<ffffffff8118472a>] ? do_getname+0x10a/0x180  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057575]  [<ffffffff8165d9be>] ? _raw_spin_lock+0xe/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057578]  [<ffffffff811964d7>] ? alloc_fd+0xf7/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057583]  [<ffffffff81178a18>] do_sys_open+0xf8/0x240  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057586]  [<ffffffff81178b80>] sys_open+0x20/0x30  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057591]  [<ffffffff81666002>] system_call_fastpath+0x16/0x1b  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.057594] INFO: task nginx:17877 blocked for more than 120 seconds.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.061709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066548] nginx           D ffffffff81806240     0 17877  17875 0x00000000  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066551]  ffff880703c07c78 0000000000000082 ffff880746bb37b0 ffff880703c07e38  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066554]  ffff880703c07fd8 ffff880703c07fd8 ffff880703c07fd8 0000000000013700  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066556]  ffff88075e5896f0 ffff880734360000 0000000000000081 ffff880746bb3bc0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066559] Call Trace:  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066562]  [<ffffffff8165badf>] schedule+0x3f/0x60  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066564]  [<ffffffff8165c8c7>] __mutex_lock_slowpath+0xd7/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066566]  [<ffffffff8165c482>] mutex_lock+0x22/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066568]  [<ffffffff81187764>] do_last+0x2b4/0x730  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066570]  [<ffffffff81188f81>] path_openat+0xd1/0x3f0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066573]  [<ffffffff8152beea>] ? sock_poll+0x1a/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066575]  [<ffffffff811893c2>] do_filp_open+0x42/0xa0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066577]  [<ffffffff8131b481>] ? strncpy_from_user+0x31/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066579]  [<ffffffff8118472a>] ? do_getname+0x10a/0x180  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066581]  [<ffffffff8165d9be>] ? _raw_spin_lock+0xe/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066584]  [<ffffffff811964d7>] ? alloc_fd+0xf7/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066586]  [<ffffffff81178a18>] do_sys_open+0xf8/0x240  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066588]  [<ffffffff81178b80>] sys_open+0x20/0x30  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066590]  [<ffffffff81666002>] system_call_fastpath+0x16/0x1b  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.066592] INFO: task nginx:17878 blocked for more than 120 seconds.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.070611] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075090] nginx           D ffffffff81806240     0 17878  17875 0x00000000  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075093]  ffff88075d68fc78 0000000000000082 ffff880746bb37b0 ffff88075d68fe38  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075098]  ffff88075d68ffd8 ffff88075d68ffd8 ffff88075d68ffd8 0000000000013700  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075103]  ffffffff81c0d020 ffff880734365bc0 0000000000000081 ffff880746bb3bc0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075109] Call Trace:  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075113]  [<ffffffff8165badf>] schedule+0x3f/0x60  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075117]  [<ffffffff8165c8c7>] __mutex_lock_slowpath+0xd7/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075120]  [<ffffffff8165c482>] mutex_lock+0x22/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075123]  [<ffffffff81187764>] do_last+0x2b4/0x730  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075127]  [<ffffffff81188f81>] path_openat+0xd1/0x3f0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075130]  [<ffffffff8152beea>] ? sock_poll+0x1a/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075134]  [<ffffffff811893c2>] do_filp_open+0x42/0xa0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075137]  [<ffffffff8131b481>] ? strncpy_from_user+0x31/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075140]  [<ffffffff8118472a>] ? do_getname+0x10a/0x180  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075143]  [<ffffffff8165d9be>] ? _raw_spin_lock+0xe/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075146]  [<ffffffff811964d7>] ? alloc_fd+0xf7/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075149]  [<ffffffff81178a18>] do_sys_open+0xf8/0x240  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075152]  [<ffffffff81178b80>] sys_open+0x20/0x30  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075156]  [<ffffffff81666002>] system_call_fastpath+0x16/0x1b  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.075158] INFO: task nginx:17879 blocked for more than 120 seconds.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.078900] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083527] nginx           D ffffffff81806240     0 17879  17875 0x00000000  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083530]  ffff880680f29c78 0000000000000082 ffff880746bb37b0 ffff880680f29e38  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083536]  ffff880680f29fd8 ffff880680f29fd8 ffff880680f29fd8 0000000000013700  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083542]  ffffffff81c0d020 ffff8807343644d0 0000000000000081 ffff880746bb3bc0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083548] Call Trace:  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083551]  [<ffffffff8165badf>] schedule+0x3f/0x60  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083554]  [<ffffffff8165c8c7>] __mutex_lock_slowpath+0xd7/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083558]  [<ffffffff8165c482>] mutex_lock+0x22/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083562]  [<ffffffff81187764>] do_last+0x2b4/0x730  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083565]  [<ffffffff81188f81>] path_openat+0xd1/0x3f0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083568]  [<ffffffff8152beea>] ? sock_poll+0x1a/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083572]  [<ffffffff811893c2>] do_filp_open+0x42/0xa0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083575]  [<ffffffff8131b481>] ? strncpy_from_user+0x31/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083578]  [<ffffffff8118472a>] ? do_getname+0x10a/0x180  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083581]  [<ffffffff8165d9be>] ? _raw_spin_lock+0xe/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083585]  [<ffffffff811964d7>] ? alloc_fd+0xf7/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083588]  [<ffffffff81178a18>] do_sys_open+0xf8/0x240  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083591]  [<ffffffff81178b80>] sys_open+0x20/0x30  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083594]  [<ffffffff81666002>] system_call_fastpath+0x16/0x1b  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.083597] INFO: task php5-fpm:15541 blocked for more than 120 seconds.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.087245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091289] php5-fpm        D 0000000000000008     0 15541  17849 0x00000004  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091291]  ffff880670031c28 0000000000000082 ffff88024683e001 00000000000043ff  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091294]  ffff880670031fd8 ffff880670031fd8 ffff880670031fd8 0000000000013700  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091299]  ffff88013cd75bc0 ffff88075ddc96f0 ffff880670031c78 ffff88074acc9cd0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091305] Call Trace:  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091309]  [<ffffffff8165badf>] schedule+0x3f/0x60  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091313]  [<ffffffff8165c8c7>] __mutex_lock_slowpath+0xd7/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091316]  [<ffffffff81185a84>] ? path_get+0x44/0x50  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091319]  [<ffffffff8165c482>] mutex_lock+0x22/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091323]  [<ffffffff81186446>] do_lookup+0x1d6/0x310  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091326]  [<ffffffff811881ac>] path_lookupat+0x11c/0x750  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091330]  [<ffffffff8114f6be>] ? free_pages_and_swap_cache+0x9e/0xc0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091334]  [<ffffffff81188811>] do_path_lookup+0x31/0xc0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091337]  [<ffffffff81189319>] user_path_at_empty+0x59/0xa0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091341]  [<ffffffff812d32cd>] ? aa_dup_task_context+0x3d/0x70  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091345]  [<ffffffff812d86bb>] ? apparmor_cred_prepare+0x3b/0x60  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091349]  [<ffffffff81189371>] user_path_at+0x11/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091352]  [<ffffffff81178212>] sys_faccessat+0xa2/0x1e0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091356]  [<ffffffff81095c3a>] ? do_gettimeofday+0x1a/0x50  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091359]  [<ffffffff81178368>] sys_access+0x18/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091363]  [<ffffffff81666002>] system_call_fastpath+0x16/0x1b  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.091368] INFO: task php5-fpm:15643 blocked for more than 120 seconds.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.094542] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098519] php5-fpm        D ffffffff81806240     0 15643  17849 0x00000000  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098522]  ffff880680d3dbb8 0000000000000086 ffff880557f73001 00000000000043ff  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098527]  ffff880680d3dfd8 ffff880680d3dfd8 ffff880680d3dfd8 0000000000013700  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098533]  ffffffff81c0d020 ffff88013cd72de0 ffff880680d3dc08 ffff88074acc9cd0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098539] Call Trace:  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098542]  [<ffffffff8165badf>] schedule+0x3f/0x60  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098545]  [<ffffffff8165c8c7>] __mutex_lock_slowpath+0xd7/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098549]  [<ffffffff81185a84>] ? path_get+0x44/0x50  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098552]  [<ffffffff8165c482>] mutex_lock+0x22/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098555]  [<ffffffff81186446>] do_lookup+0x1d6/0x310  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098558]  [<ffffffff811881ac>] path_lookupat+0x11c/0x750  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098561]  [<ffffffff81188811>] do_path_lookup+0x31/0xc0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098564]  [<ffffffff81189319>] user_path_at_empty+0x59/0xa0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098568]  [<ffffffff8113e127>] ? zap_page_range+0xb7/0xd0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098572]  [<ffffffff8165d9be>] ? _raw_spin_lock+0xe/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098575]  [<ffffffff8109f8f3>] ? futex_wake+0x113/0x130  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098578]  [<ffffffff81189371>] user_path_at+0x11/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098582]  [<ffffffff8117e39a>] vfs_fstatat+0x3a/0x70  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098585]  [<ffffffff8117e3ee>] vfs_lstat+0x1e/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098588]  [<ffffffff8117e58a>] sys_newlstat+0x1a/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098591]  [<ffffffff8113a855>] ? sys_madvise+0x225/0x280  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098595]  [<ffffffff81666002>] system_call_fastpath+0x16/0x1b  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.098598] INFO: task php5-fpm:15775 blocked for more than 120 seconds.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.102580] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107285] php5-fpm        D ffffffff81806240     0 15775  17849 0x00000000  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107287]  ffff880680f69bb8 0000000000000086 ffff88074bdce001 00000000000043ff  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107292]  ffff880680f69fd8 ffff880680f69fd8 ffff880680f69fd8 0000000000013700  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107298]  ffff88075e5a96f0 ffff88074bbf8000 ffff880680f69c08 ffff88074acc9cd0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107303] Call Trace:  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107307]  [<ffffffff8165badf>] schedule+0x3f/0x60  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107311]  [<ffffffff8165c8c7>] __mutex_lock_slowpath+0xd7/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107314]  [<ffffffff81185a84>] ? path_get+0x44/0x50  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107317]  [<ffffffff8165c482>] mutex_lock+0x22/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107320]  [<ffffffff81186446>] do_lookup+0x1d6/0x310  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107323]  [<ffffffff811881ac>] path_lookupat+0x11c/0x750  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107327]  [<ffffffff810d8ea7>] ? irq_to_desc+0x17/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107331]  [<ffffffff810dbd8e>] ? irq_get_irq_data+0xe/0x10  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107334]  [<ffffffff81188811>] do_path_lookup+0x31/0xc0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107337]  [<ffffffff81189319>] user_path_at_empty+0x59/0xa0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107340]  [<ffffffff8165d9be>] ? _raw_spin_lock+0xe/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107344]  [<ffffffff8109f8f3>] ? futex_wake+0x113/0x130  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107347]  [<ffffffff81189371>] user_path_at+0x11/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107351]  [<ffffffff8117e39a>] vfs_fstatat+0x3a/0x70  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107354]  [<ffffffff8117e3ee>] vfs_lstat+0x1e/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107357]  [<ffffffff8117e58a>] sys_newlstat+0x1a/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107361]  [<ffffffff81666002>] system_call_fastpath+0x16/0x1b  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.107364] INFO: task php5-fpm:16184 blocked for more than 120 seconds.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.110831] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115362] php5-fpm        D ffffffff81806240     0 16184  17849 0x00000004  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115364]  ffff88070499dbb8 0000000000000082 ffff880037452001 00000000000043ff  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115370]  ffff88070499dfd8 ffff88070499dfd8 ffff88070499dfd8 0000000000013700  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115376]  ffff88075e6196f0 ffff8807309cc4d0 ffff88070499dc08 ffff88074acc9cd0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115381] Call Trace:  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115385]  [<ffffffff8165badf>] schedule+0x3f/0x60  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115388]  [<ffffffff8165c8c7>] __mutex_lock_slowpath+0xd7/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115391]  [<ffffffff81185a84>] ? path_get+0x44/0x50  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115394]  [<ffffffff8165c482>] mutex_lock+0x22/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115397]  [<ffffffff81186446>] do_lookup+0x1d6/0x310  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115400]  [<ffffffff811881ac>] path_lookupat+0x11c/0x750  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115404]  [<ffffffff81188811>] do_path_lookup+0x31/0xc0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115407]  [<ffffffff81189319>] user_path_at_empty+0x59/0xa0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115410]  [<ffffffff8165d9be>] ? _raw_spin_lock+0xe/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115413]  [<ffffffff8109f8f3>] ? futex_wake+0x113/0x130  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115416]  [<ffffffff81189371>] user_path_at+0x11/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115420]  [<ffffffff8117e39a>] vfs_fstatat+0x3a/0x70  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115423]  [<ffffffff8117e3ee>] vfs_lstat+0x1e/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115427]  [<ffffffff8117e58a>] sys_newlstat+0x1a/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115431]  [<ffffffff81080b0a>] ? do_sys_times+0xaa/0xc0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115434]  [<ffffffff81080b6a>] ? sys_times+0x4a/0x60  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115437]  [<ffffffff81666002>] system_call_fastpath+0x16/0x1b  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.115440] INFO: task php5-fpm:16213 blocked for more than 120 seconds.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.118940] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123356] php5-fpm        D ffffffff81806240     0 16213  17849 0x00000004  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123358]  ffff880730811bb8 0000000000000086 ffff8804f99e0001 00000000000043ff  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123363]  ffff880730811fd8 ffff880730811fd8 ffff880730811fd8 0000000000013700  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123369]  ffff88075e5a96f0 ffff8806d47f44d0 ffff880730811c08 ffff88074acc9cd0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123374] Call Trace:  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123378]  [<ffffffff8165badf>] schedule+0x3f/0x60  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123381]  [<ffffffff8165c8c7>] __mutex_lock_slowpath+0xd7/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123384]  [<ffffffff81185a84>] ? path_get+0x44/0x50  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123387]  [<ffffffff8165c482>] mutex_lock+0x22/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123390]  [<ffffffff81186446>] do_lookup+0x1d6/0x310  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123393]  [<ffffffff811881ac>] path_lookupat+0x11c/0x750  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123397]  [<ffffffff81188811>] do_path_lookup+0x31/0xc0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123400]  [<ffffffff81189319>] user_path_at_empty+0x59/0xa0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123403]  [<ffffffff8113e127>] ? zap_page_range+0xb7/0xd0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123406]  [<ffffffff8165d9be>] ? _raw_spin_lock+0xe/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123410]  [<ffffffff8109f8f3>] ? futex_wake+0x113/0x130  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123413]  [<ffffffff81189371>] user_path_at+0x11/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123416]  [<ffffffff8117e39a>] vfs_fstatat+0x3a/0x70  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123420]  [<ffffffff8117e3ee>] vfs_lstat+0x1e/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123423]  [<ffffffff8117e58a>] sys_newlstat+0x1a/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123426]  [<ffffffff8113a855>] ? sys_madvise+0x225/0x280  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123429]  [<ffffffff81666002>] system_call_fastpath+0x16/0x1b  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.123434] INFO: task php5-fpm:17429 blocked for more than 120 seconds.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.127444] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131732] php5-fpm        D ffffffff81806240     0 17429  17849 0x00000004  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131735]  ffff88063481dbb8 0000000000000086 ffff880634995001 00000000000043ff  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131740]  ffff88063481dfd8 ffff88063481dfd8 ffff88063481dfd8 0000000000013700  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131746]  ffff88075e7796f0 ffff88075d0896f0 ffff88063481dc08 ffff88074acc9cd0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131751] Call Trace:  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131755]  [<ffffffff8165badf>] schedule+0x3f/0x60  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131758]  [<ffffffff8165c8c7>] __mutex_lock_slowpath+0xd7/0x150  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131762]  [<ffffffff81185a84>] ? path_get+0x44/0x50  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131765]  [<ffffffff8165c482>] mutex_lock+0x22/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131768]  [<ffffffff81186446>] do_lookup+0x1d6/0x310  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131771]  [<ffffffff811881ac>] path_lookupat+0x11c/0x750  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131774]  [<ffffffff810d8ea7>] ? irq_to_desc+0x17/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131777]  [<ffffffff810dbd8e>] ? irq_get_irq_data+0xe/0x10  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131780]  [<ffffffff81188811>] do_path_lookup+0x31/0xc0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131784]  [<ffffffff81189319>] user_path_at_empty+0x59/0xa0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131787]  [<ffffffff8165d9be>] ? _raw_spin_lock+0xe/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131790]  [<ffffffff8109f8f3>] ? futex_wake+0x113/0x130  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131794]  [<ffffffff81189371>] user_path_at+0x11/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131797]  [<ffffffff8117e39a>] vfs_fstatat+0x3a/0x70  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131800]  [<ffffffff8117e3ee>] vfs_lstat+0x1e/0x20  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131803]  [<ffffffff8117e58a>] sys_newlstat+0x1a/0x40  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131807]  [<ffffffff81080b0a>] ? do_sys_times+0xaa/0xc0  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131810]  [<ffffffff81080b6a>] ? sys_times+0x4a/0x60  Jan 31 22:51:25 ip-10-0-0-160 kernel: [115562.131814]  [<ffffffff81666002>] system_call_fastpath+0x16/0x1b  

How do I ensure that such cases, doesn't create HIGH DISK IO / Server Unstable?

apache mod proxy_wstunnel invalid utf8 during websocket upgrade

Posted: 11 Jun 2021 10:02 AM PDT

I am experiencing an intermittent problem when connecting the jetty web-socket client to the server. The good people at Jetty assure me it is not a problem with Jetty.

On the server side I have apache with mod proxy_wstunnel proxying to tomcat 7.

When I take apache out of the picture and connect the client directly to tomcat, the error seems to disappear. Also the error does not seem to happen when I run the client on linux, the problem only seems to occur on windows 7.

I've noticed that apache is returning a 500 html page at some stage, however, even if I set the loglevel to debug, I don't get any useful information on how to resolve the error.

If anyone could help me figure out how to resolve this it would be much appreciated. Hours of googling have not helped.

The software versions are:

apache Server version: Apache/2.4.7 (Ubuntu), Server built: Jul 22 2014 14:36:38 tomcat Apache Tomcat/7.0.52 (Ubuntu) 1.8.0_25-b17 Oracle Corporation Linux 3.13.0-32-generic Jetty client: 9.2.6.v20141205

The apache wstunnel config:

      <VirtualHost *:80>                ServerName ws.redacted.io                ServerAdmin webmaster@localhost                ErrorLog ${APACHE_LOG_DIR}/error.log              CustomLog ${APACHE_LOG_DIR}/access.log combined                <Directory />                      AllowOverride none                      Require all denied              </Directory>          LogLevel debug              ProxyPass /redacted-srv/ ws://localhost:8080/redacted-srv/              ProxyPassReverse /redacted-srv/ ws://localhost:8080/redacted-srv/        </VirtualHost>  

The apache error log:

      [Mon Dec 29 13:33:21.355169 2014] [mpm_event:notice] [pid 1074:tid 140252728342400] AH00491: caught SIGTERM, shutting down      [Mon Dec 29 13:33:22.141202 2014] [mpm_event:notice] [pid 9328:tid 140463177648000] AH00489: Apache/2.4.7 (Ubuntu) mod_jk/1.2.37 configured -- resuming normal operations      [Mon Dec 29 13:33:22.141279 2014] [core:notice] [pid 9328:tid 140463177648000] AH00094: Command line: '/usr/sbin/apache2'      [Mon Dec 29 13:33:22.141935 2014] [proxy:debug] [pid 9331:tid 140463177648000] proxy_util.c(1694): AH00925: initializing worker ws://localhost:8080/redacted-srv/ shared      [Mon Dec 29 13:33:22.141977 2014] [proxy:debug] [pid 9331:tid 140463177648000] proxy_util.c(1734): AH00927: initializing worker ws://localhost:8080/redacted-srv/ local      [Mon Dec 29 13:33:22.141993 2014] [proxy:debug] [pid 9331:tid 140463177648000] proxy_util.c(1769): AH00930: initialized pool in child 9331 for (localhost) min=0 max=25 smax=25      [Mon Dec 29 13:33:22.142526 2014] [proxy:debug] [pid 9330:tid 140463177648000] proxy_util.c(1694): AH00925: initializing worker ws://localhost:8080/redacted-srv/ shared      [Mon Dec 29 13:33:22.142574 2014] [proxy:debug] [pid 9330:tid 140463177648000] proxy_util.c(1734): AH00927: initializing worker ws://localhost:8080/redacted-srv/ local      [Mon Dec 29 13:33:22.142595 2014] [proxy:debug] [pid 9330:tid 140463177648000] proxy_util.c(1769): AH00930: initialized pool in child 9330 for (localhost) min=0 max=25 smax=25      [Mon Dec 29 13:33:33.367328 2014] [authz_core:debug] [pid 9331:tid 140463053694720] mod_authz_core.c(828): [client 105.210.40.30:50872] AH01628: authorization result: granted (no directives)      [Mon Dec 29 13:33:33.367463 2014] [proxy:debug] [pid 9331:tid 140463053694720] mod_proxy.c(1104): [client 105.210.40.30:50872] AH01143: Running scheme ws handler (attempt 0)      [Mon Dec 29 13:33:33.367483 2014] [proxy_http:debug] [pid 9331:tid 140463053694720] mod_proxy_http.c(1892): [client 105.210.40.30:50872] AH01113: HTTP: declining URL ws://localhost:8080/redacted-srv/ws      [Mon Dec 29 13:33:33.367493 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463053694720] mod_proxy_wstunnel.c(331): [client 105.210.40.30:50872] AH02451: serving URL ws://localhost:8080/redacted-srv/ws      [Mon Dec 29 13:33:33.367517 2014] [proxy:debug] [pid 9331:tid 140463053694720] proxy_util.c(2020): AH00942: WS: has acquired connection for (localhost)      [Mon Dec 29 13:33:33.367526 2014] [proxy:debug] [pid 9331:tid 140463053694720] proxy_util.c(2072): [client 105.210.40.30:50872] AH00944: connecting ws://localhost:8080/redacted-srv/ws to localhost:8080      [Mon Dec 29 13:33:33.367767 2014] [proxy:debug] [pid 9331:tid 140463053694720] proxy_util.c(2206): [client 105.210.40.30:50872] AH00947: connected /redacted-srv/ws to localhost:8080      [Mon Dec 29 13:33:33.367913 2014] [proxy:debug] [pid 9331:tid 140463053694720] proxy_util.c(2610): AH00962: WS: connection complete to 127.0.0.1:8080 (localhost)      [Mon Dec 29 13:33:33.384725 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463053694720] mod_proxy_wstunnel.c(253): [client 105.210.40.30:50872] AH02445: woke from poll(), i=1      [Mon Dec 29 13:33:33.384776 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463053694720] mod_proxy_wstunnel.c(262): [client 105.210.40.30:50872] AH02446: sock was readable      [Mon Dec 29 13:33:33.811469 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463053694720] mod_proxy_wstunnel.c(253): [client 105.210.40.30:50872] AH02445: woke from poll(), i=1      [Mon Dec 29 13:33:33.811558 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463053694720] mod_proxy_wstunnel.c(278): [client 105.210.40.30:50872] AH02448: client was readable      [Mon Dec 29 13:33:33.858796 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463053694720] mod_proxy_wstunnel.c(253): [client 105.210.40.30:50872] AH02445: woke from poll(), i=1      [Mon Dec 29 13:33:33.858827 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463053694720] mod_proxy_wstunnel.c(262): [client 105.210.40.30:50872] AH02446: sock was readable      [Mon Dec 29 13:33:33.860386 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463053694720] mod_proxy_wstunnel.c(253): [client 105.210.40.30:50872] AH02445: woke from poll(), i=1      [Mon Dec 29 13:33:33.860400 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463053694720] mod_proxy_wstunnel.c(262): [client 105.210.40.30:50872] AH02446: sock was readable      [Mon Dec 29 13:34:02.718967 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463053694720] mod_proxy_wstunnel.c(253): [client 105.210.40.30:50872] AH02445: woke from poll(), i=1      [Mon Dec 29 13:34:02.719083 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463053694720] mod_proxy_wstunnel.c(278): [client 105.210.40.30:50872] AH02448: client was readable      [Mon Dec 29 13:34:02.719152 2014] [proxy:debug] [pid 9331:tid 140463053694720] proxy_util.c(2035): AH00943: WS: has released connection for (localhost)      [Mon Dec 29 13:34:10.503173 2014] [authz_core:debug] [pid 9330:tid 140463078872832] mod_authz_core.c(828): [client 105.210.40.30:50890] AH01628: authorization result: granted (no directives)      [Mon Dec 29 13:34:10.503299 2014] [proxy:debug] [pid 9330:tid 140463078872832] mod_proxy.c(1104): [client 105.210.40.30:50890] AH01143: Running scheme ws handler (attempt 0)      [Mon Dec 29 13:34:10.503313 2014] [proxy_http:debug] [pid 9330:tid 140463078872832] mod_proxy_http.c(1892): [client 105.210.40.30:50890] AH01113: HTTP: declining URL ws://localhost:8080/redacted-srv/ws      [Mon Dec 29 13:34:10.503329 2014] [proxy_wstunnel:debug] [pid 9330:tid 140463078872832] mod_proxy_wstunnel.c(331): [client 105.210.40.30:50890] AH02451: serving URL ws://localhost:8080/redacted-srv/ws      [Mon Dec 29 13:34:10.503349 2014] [proxy:debug] [pid 9330:tid 140463078872832] proxy_util.c(2020): AH00942: WS: has acquired connection for (localhost)      [Mon Dec 29 13:34:10.503357 2014] [proxy:debug] [pid 9330:tid 140463078872832] proxy_util.c(2072): [client 105.210.40.30:50890] AH00944: connecting ws://localhost:8080/redacted-srv/ws to localhost:8080      [Mon Dec 29 13:34:10.503618 2014] [proxy:debug] [pid 9330:tid 140463078872832] proxy_util.c(2206): [client 105.210.40.30:50890] AH00947: connected /redacted-srv/ws to localhost:8080      [Mon Dec 29 13:34:10.503781 2014] [proxy:debug] [pid 9330:tid 140463078872832] proxy_util.c(2610): AH00962: WS: connection complete to 127.0.0.1:8080 (localhost)      [Mon Dec 29 13:34:10.507443 2014] [proxy_wstunnel:debug] [pid 9330:tid 140463078872832] mod_proxy_wstunnel.c(253): [client 105.210.40.30:50890] AH02445: woke from poll(), i=1      [Mon Dec 29 13:34:10.507463 2014] [proxy_wstunnel:debug] [pid 9330:tid 140463078872832] mod_proxy_wstunnel.c(262): [client 105.210.40.30:50890] AH02446: sock was readable      [Mon Dec 29 13:34:10.967619 2014] [proxy_wstunnel:debug] [pid 9330:tid 140463078872832] mod_proxy_wstunnel.c(253): [client 105.210.40.30:50890] AH02445: woke from poll(), i=1      [Mon Dec 29 13:34:10.967682 2014] [proxy_wstunnel:debug] [pid 9330:tid 140463078872832] mod_proxy_wstunnel.c(278): [client 105.210.40.30:50890] AH02448: client was readable      [Mon Dec 29 13:34:10.993060 2014] [proxy_wstunnel:debug] [pid 9330:tid 140463078872832] mod_proxy_wstunnel.c(253): [client 105.210.40.30:50890] AH02445: woke from poll(), i=1      [Mon Dec 29 13:34:10.993093 2014] [proxy_wstunnel:debug] [pid 9330:tid 140463078872832] mod_proxy_wstunnel.c(262): [client 105.210.40.30:50890] AH02446: sock was readable      [Mon Dec 29 13:34:10.996379 2014] [proxy_wstunnel:debug] [pid 9330:tid 140463078872832] mod_proxy_wstunnel.c(253): [client 105.210.40.30:50890] AH02445: woke from poll(), i=1      [Mon Dec 29 13:34:10.996421 2014] [proxy_wstunnel:debug] [pid 9330:tid 140463078872832] mod_proxy_wstunnel.c(262): [client 105.210.40.30:50890] AH02446: sock was readable      [Mon Dec 29 13:34:39.916202 2014] [proxy_wstunnel:debug] [pid 9330:tid 140463078872832] mod_proxy_wstunnel.c(253): [client 105.210.40.30:50890] AH02445: woke from poll(), i=1      [Mon Dec 29 13:34:39.916286 2014] [proxy_wstunnel:debug] [pid 9330:tid 140463078872832] mod_proxy_wstunnel.c(278): [client 105.210.40.30:50890] AH02448: client was readable      [Mon Dec 29 13:34:39.916378 2014] [proxy:debug] [pid 9330:tid 140463078872832] proxy_util.c(2035): AH00943: WS: has released connection for (localhost)      [Mon Dec 29 13:34:45.982784 2014] [authz_core:debug] [pid 9331:tid 140463062087424] mod_authz_core.c(828): [client 105.210.40.30:50911] AH01628: authorization result: granted (no directives)      [Mon Dec 29 13:34:45.982890 2014] [proxy:debug] [pid 9331:tid 140463062087424] mod_proxy.c(1104): [client 105.210.40.30:50911] AH01143: Running scheme ws handler (attempt 0)      [Mon Dec 29 13:34:45.982900 2014] [proxy_http:debug] [pid 9331:tid 140463062087424] mod_proxy_http.c(1892): [client 105.210.40.30:50911] AH01113: HTTP: declining URL ws://localhost:8080/redacted-srv/ws      [Mon Dec 29 13:34:45.982907 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463062087424] mod_proxy_wstunnel.c(331): [client 105.210.40.30:50911] AH02451: serving URL ws://localhost:8080/redacted-srv/ws      [Mon Dec 29 13:34:45.982927 2014] [proxy:debug] [pid 9331:tid 140463062087424] proxy_util.c(2020): AH00942: WS: has acquired connection for (localhost)      [Mon Dec 29 13:34:45.982947 2014] [proxy:debug] [pid 9331:tid 140463062087424] proxy_util.c(2072): [client 105.210.40.30:50911] AH00944: connecting ws://localhost:8080/redacted-srv/ws to localhost:8080      [Mon Dec 29 13:34:45.982957 2014] [proxy:debug] [pid 9331:tid 140463062087424] proxy_util.c(2206): [client 105.210.40.30:50911] AH00947: connected /redacted-srv/ws to localhost:8080      [Mon Dec 29 13:34:45.983079 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463062087424] mod_proxy_wstunnel.c(253): [client 105.210.40.30:50911] AH02445: woke from poll(), i=1      [Mon Dec 29 13:34:45.983090 2014] [proxy_wstunnel:debug] [pid 9331:tid 140463062087424] mod_proxy_wstunnel.c(262): [client 105.210.40.30:50911] AH02446: sock was readable      [Mon Dec 29 13:34:45.983171 2014] [proxy:debug] [pid 9331:tid 140463062087424] proxy_util.c(2035): AH00943: WS: has     released connection for (localhost)  

The ngrep output on port 80 (between apache and the websocket client)

  filter: (ip or ip6) and ( port 80 )      #      T 105.210.y.y:49975 -> 104.131.x.x:80 [S]      #      T 104.131.x.x:80 -> 105.210.y.y:49975 [AS]      #      T 105.210.y.y:49975 -> 104.131.x.x:80 [A]        00 00 00 00 00 00                                     ......
# T 105.210.y.y:49975 -> 104.131.x.x:80 [AP] 47 45 54 20 2f 74 72 61 6e 73 6c 61 74 6f 72 2d GET /trandomain- 73 72 76 2f 77 73 20 48 54 54 50 2f 31 2e 31 0d srv/ws HTTP/1.1. 0a 48 6f 73 74 3a 20 77 73 2e 73 6c 61 74 6f 72 .Host: ws.domain 2e 69 6f 0d 0a 55 70 67 72 61 64 65 3a 20 77 65 .io..Upgrade: we 62 73 6f 63 6b 65 74 0d 0a 43 6f 6e 6e 65 63 74 bsocket..Connect 69 6f 6e 3a 20 55 70 67 72 61 64 65 0d 0a 53 65 ion: Upgrade..Se 63 2d 57 65 62 53 6f 63 6b 65 74 2d 4b 65 79 3a c-WebSocket-Key: 20 56 50 54 4a 79 42 6b 30 36 38 65 7a 66 30 62 VPTJyBk068ezf0b 34 57 66 41 39 73 51 3d 3d 0d 0a 53 65 63 2d 57 4WfA9sQ==..Sec-W 65 62 53 6f 63 6b 65 74 2d 56 65 72 73 69 6f 6e ebSocket-Version 3a 20 31 33 0d 0a 50 72 61 67 6d 61 3a 20 6e 6f : 13..Pragma: no 2d 63 61 63 68 65 0d 0a 43 61 63 68 65 2d 43 6f -cache..Cache-Co 6e 74 72 6f 6c 3a 20 6e 6f 2d 63 61 63 68 65 0d ntrol: no-cache. 0a 0d 0a ...
# T 104.131.x.x:80 -> 105.210.y.y:49975 [A] # T 104.131.x.x:80 -> 105.210.y.y:49975 [AP] 48 54 54 50 2f 31 2e 31 20 31 30 31 20 53 77 69 HTTP/1.1 101 Swi 74 63 68 69 6e 67 20 50 72 6f 74 6f 63 6f 6c 73 tching Protocols 0d 0a 53 65 72 76 65 72 3a 20 41 70 61 63 68 65 ..Server: Apache 2d 43 6f 79 6f 74 65 2f 31 2e 31 0d 0a 55 70 67 -Coyote/1.1..Upg 72 61 64 65 3a 20 77 65 62 73 6f 63 6b 65 74 0d rade: websocket. 0a 43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 75 70 67 .Connection: upg 72 61 64 65 0d 0a 53 65 63 2d 57 65 62 53 6f 63 rade..Sec-WebSoc 6b 65 74 2d 41 63 63 65 70 74 3a 20 31 4a 51 76 ket-Accept: 1JQv 41 2f 43 56 55 5a 38 59 6d 4d 4a 38 70 62 33 53 A/CVUZ8YmMJ8pb3S 48 33 51 47 56 4e 34 3d 0d 0a 44 61 74 65 3a 20 H3QGVN4=..Date: 57 65 64 2c 20 32 34 20 44 65 63 20 32 30 31 34 Wed, 24 Dec 2014 20 31 34 3a 33 31 3a 31 37 20 47 4d 54 0d 0a 0d 14:31:17 GMT... 0a .
# T 105.210.y.y:49975 -> 104.131.x.x:80 [AP] 82 9c ea 9e d0 54 e2 9e c3 1e eb af c4 47 a0 98 .....T.......G.. a4 31 99 ea e1 61 fe 8d 9a 53 9e fb a3 20 db ac .1...a...S... .. e3 40 .@
# T 104.131.x.x:80 -> 105.210.y.y:49975 [A] # T 104.131.x.x:80 -> 105.210.y.y:49975 [AP] 82 09 ..
# T 104.131.x.x:80 -> 105.210.y.y:49975 [AP] 08 00 13 4a 03 32 37 30 14 ...J.270.
# T 105.210.y.y:49975 -> 104.131.x.x:80 [A] 00 00 00 00 00 00 ......
# T 105.210.y.y:49975 -> 104.131.x.x:80 [AP] 88 8a bc 23 03 08 bf ca 50 60 c9 57 67 67 cb 4d ...#....P.Wgg.M # T 104.131.x.x:80 -> 105.210.y.y:49975 [A] # T 105.210.y.y:49975 -> 104.131.x.x:80 [AF] 00 00 00 00 00 00 ......
# T 104.131.x.x:80 -> 105.210.y.y:49975 [AF] # T 105.210.y.y:49975 -> 104.131.x.x:80 [AFP] 88 8a bc 23 03 08 bf ca 50 60 c9 57 67 67 cb 4d ...#....P
.Wgg.M # T 104.131.x.x:80 -> 105.210.y.y:49975 [A] # T 105.210.y.y:49975 -> 104.131.x.x:80 [AFP] 88 8a bc 23 03 08 bf ca 50 60 c9 57 67 67 cb 4d ...#....P.Wgg.M # T 104.131.x.x:80 -> 105.210.y.y:49975 [A] # T 104.131.x.x:80 -> 105.210.y.y:49975 [AF] # T 105.210.y.y:49975 -> 104.131.x.x:80 [AFP] 88 8a bc 23 03 08 bf ca 50 60 c9 57 67 67 cb 4d ...#....P.Wgg.M # T 104.131.x.x:80 -> 105.210.y.y:49975 [A] # T 104.131.x.x:80 -> 105.210.y.y:49975 [AF] # T 105.210.y.y:49983 -> 104.131.x.x:80 [S] # T 104.131.x.x:80 -> 105.210.y.y:49983 [AS] # T 105.210.y.y:49983 -> 104.131.x.x:80 [A] 00 00 00 00 00 00 ......
# T 105.210.y.y:49983 -> 104.131.x.x:80 [AP] 47 45 54 20 2f 74 72 61 6e 73 6c 61 74 6f 72 2d GET /trandomain- 73 72 76 2f 77 73 20 48 54 54 50 2f 31 2e 31 0d srv/ws HTTP/1.1. 0a 48 6f 73 74 3a 20 77 73 2e 73 6c 61 74 6f 72 .Host: ws.domain 2e 69 6f 0d 0a 55 70 67 72 61 64 65 3a 20 77 65 .io..Upgrade: we 62 73 6f 63 6b 65 74 0d 0a 43 6f 6e 6e 65 63 74 bsocket..Connect 69 6f 6e 3a 20 55 70 67 72 61 64 65 0d 0a 53 65 ion: Upgrade..Se 63 2d 57 65 62 53 6f 63 6b 65 74 2d 4b 65 79 3a c-WebSocket-Key: 20 53 35 65 55 79 36 78 6a 55 53 70 51 46 57 47 S5eUy6xjUSpQFWG 37 2b 4a 4d 66 2b 51 3d 3d 0d 0a 53 65 63 2d 57 7+JMf+Q==..Sec-W 65 62 53 6f 63 6b 65 74 2d 56 65 72 73 69 6f 6e ebSocket-Version 3a 20 31 33 0d 0a 50 72 61 67 6d 61 3a 20 6e 6f : 13..Pragma: no 2d 63 61 63 68 65 0d 0a 43 61 63 68 65 2d 43 6f -cache..Cache-Co 6e 74 72 6f 6c 3a 20 6e 6f 2d 63 61 63 68 65 0d ntrol: no-cache. 0a 0d 0a ...
# T 104.131.x.x:80 -> 105.210.y.y:49983 [A] # T 104.131.x.x:80 -> 105.210.y.y:49983 [AP] 48 54 54 50 2f 31 2e 31 20 31 30 31 20 53 77 69 HTTP/1.1 101 Swi 74 63 68 69 6e 67 20 50 72 6f 74 6f 63 6f 6c 73 tching Protocols 0d 0a 53 65 72 76 65 72 3a 20 41 70 61 63 68 65 ..Server: Apache 2d 43 6f 79 6f 74 65 2f 31 2e 31 0d 0a 55 70 67 -Coyote/1.1..Upg 72 61 64 65 3a 20 77 65 62 73 6f 63 6b 65 74 0d rade: websocket. 0a 43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 75 70 67 .Connection: upg 72 61 64 65 0d 0a 53 65 63 2d 57 65 62 53 6f 63 rade..Sec-WebSoc 6b 65 74 2d 41 63 63 65 70 74 3a 20 52 56 43 4b ket-Accept: RVCK 72 41 6c 7a 59 30 66 4b 38 38 61 4d 43 30 61 37 rAlzY0fK88aMC0a7 6e 31 74 62 35 71 38 3d 0d 0a 44 61 74 65 3a 20 n1tb5q8=..Date: 57 65 64 2c 20 32 34 20 44 65 63 20 32 30 31 34 Wed, 24 Dec 2014 20 31 34 3a 33 31 3a 33 39 20 47 4d 54 0d 0a 0d 14:31:39 GMT... 0a .
# T 104.131.x.x:80 -> 105.210.y.y:49975 [AF] # T 105.210.y.y:49983 -> 104.131.x.x:80 [A] 00 00 00 00 00 00 ......
# T 105.210.y.y:49983 -> 104.131.x.x:80 [AP] 82 9c a1 86 a8 97 a9 86 bb dd a0 b7 bc 84 eb 80 ................ dc f2 d2 f2 99 a2 b5 95 e2 90 d5 e3 db e3 90 b4 ................ 9b 83 ..
# T 104.131.x.x:80 -> 105.210.y.y:49983 [AP] 82 09 ..
# T 104.131.x.x:80 -> 105.210.y.y:49983 [AP] 08 00 13 4a 03 32 37 30 14 ...J.270.
# T 105.210.y.y:49975 -> 104.131.x.x:80 [AFP] 88 8a bc 23 03 08 bf ca 50 60 c9 57 67 67 cb 4d ...#....P.Wgg.M # T 104.131.x.x:80 -> 105.210.y.y:49975 [A] # T 105.210.y.y:49983 -> 104.131.x.x:80 [A] 00 00 00 00 00 00 ......
# T 104.131.x.x:80 -> 105.210.y.y:49975 [AF] # T 105.210.y.y:49975 -> 104.131.x.x:80 [AFP] 88 8a bc 23 03 08 bf ca 50 60 c9 57 67 67 cb 4d ...#....P
.Wgg.M # T 104.131.x.x:80 -> 105.210.y.y:49975 [A] # T 105.210.y.y:49983 -> 104.131.x.x:80 [AP] 88 8a ad d9 9f c4 ae 30 cc ac d8 ad fb ab da b7 .......0........ # T 105.210.y.y:49983 -> 104.131.x.x:80 [AF] 00 00 00 00 00 00 ......
# T 104.131.x.x:80 -> 105.210.y.y:49983 [AF] # T 105.210.y.y:49983 -> 104.131.x.x:80 [AFP] 88 8a ad d9 9f c4 ae 30 cc ac d8 ad fb ab da b7 .......0........ # T 104.131.x.x:80 -> 105.210.y.y:49983 [A] # T 105.210.y.y:49983 -> 104.131.x.x:80 [AFP] 88 8a ad d9 9f c4 ae 30 cc ac d8 ad fb ab da b7 .......0........ # T 104.131.x.x:80 -> 105.210.y.y:49983 [A] # T 104.131.x.x:80 -> 105.210.y.y:49983 [AF] # T 105.210.y.y:49983 -> 104.131.x.x:80 [AFP] 88 8a ad d9 9f c4 ae 30 cc ac d8 ad fb ab da b7 .......0........ # T 104.131.x.x:80 -> 105.210.y.y:49983 [A] # T 104.131.x.x:80 -> 105.210.y.y:49983 [AF] # T 105.210.y.y:49991 -> 104.131.x.x:80 [S] # T 104.131.x.x:80 -> 105.210.y.y:49991 [AS] # T 104.131.x.x:80 -> 105.210.y.y:49975 [AF] # T 105.210.y.y:49991 -> 104.131.x.x:80 [A] 00 00 00 00 00 00 ......
# T 105.210.y.y:49991 -> 104.131.x.x:80 [AP] 47 45 54 20 2f 74 72 61 6e 73 6c 61 74 6f 72 2d GET /trandomain- 73 72 76 2f 77 73 20 48 54 54 50 2f 31 2e 31 0d srv/ws HTTP/1.1. 0a 48 6f 73 74 3a 20 77 73 2e 73 6c 61 74 6f 72 .Host: ws.domain 2e 69 6f 0d 0a 55 70 67 72 61 64 65 3a 20 77 65 .io..Upgrade: we 62 73 6f 63 6b 65 74 0d 0a 43 6f 6e 6e 65 63 74 bsocket..Connect 69 6f 6e 3a 20 55 70 67 72 61 64 65 0d 0a 53 65 ion: Upgrade..Se 63 2d 57 65 62 53 6f 63 6b 65 74 2d 4b 65 79 3a c-WebSocket-Key: 20 62 45 54 54 44 72 77 54 75 69 64 4f 67 4a 4a bETTDrwTuidOgJJ 68 73 56 7a 31 4c 41 3d 3d 0d 0a 53 65 63 2d 57 hsVz1LA==..Sec-W 65 62 53 6f 63 6b 65 74 2d 56 65 72 73 69 6f 6e ebSocket-Version 3a 20 31 33 0d 0a 50 72 61 67 6d 61 3a 20 6e 6f : 13..Pragma: no 2d 63 61 63 68 65 0d 0a 43 61 63 68 65 2d 43 6f -cache..Cache-Co 6e 74 72 6f 6c 3a 20 6e 6f 2d 63 61 63 68 65 0d ntrol: no-cache. 0a 0d 0a ...
# T 104.131.x.x:80 -> 105.210.y.y:49991 [A] # T 104.131.x.x:80 -> 105.210.y.y:49991 [AP] 88 0a 03 e9 53 68 75 74 64 6f 77 6e ....Shutdown
# T 104.131.x.x:80 -> 105.210.y.y:49991 [AP] 3c 21 44 4f 43 54 59 50 45 20 48 54 4d 4c 20 50 .. 3c 74 69 74 6c 65 3e 35 30 30 20 49 6e 74 65 72 500 Inter 6e 61 6c 20 53 65 72 76 65 72 20 45 72 72 6f 72 nal Server Error 3c 2f 74 69 74 6c 65 3e 0a 3c 2f 68 65 61 64 3e . 3c 62 6f 64 79 3e 0a 3c 68 31 3e 49 6e 74 65 72 . Inter 6e 61 6c 20 53 65 72 76 65 72 20 45 72 72 6f 72 nal Server Error 3c 2f 68 31 3e 0a 3c 70 3e 54 68 65 20 73 65 72
. The ser 76 65 72 20 65 6e 63 6f 75 6e 74 65 72 65 64 20 ver encountered 61 6e 20 69 6e 74 65 72 6e 61 6c 20 65 72 72 6f an internal erro 72 20 6f 72 0a 6d 69 73 63 6f 6e 66 69 67 75 72 r or.misconfigur 61 74 69 6f 6e 20 61 6e 64 20 77 61 73 20 75 6e ation and was un 61 62 6c 65 20 74 6f 20 63 6f 6d 70 6c 65 74 65 able to complete 0a 79 6f 75 72 20 72 65 71 75 65 73 74 2e 3c 2f .your request..

Please con 74 61 63 74 20 74 68 65 20 73 65 72 76 65 72 20 tact the server 61 64 6d 69 6e 69 73 74 72 61 74 6f 72 20 61 74 administrator at 20 0a 20 77 65 62 6d 61 73 74 65 72 40 6c 6f 63 . webmaster@loc 61 6c 68 6f 73 74 20 74 6f 20 69 6e 66 6f 72 6d alhost to inform 20 74 68 65 6d 20 6f 66 20 74 68 65 20 74 69 6d them of the tim 65 20 74 68 69 73 20 65 72 72 6f 72 20 6f 63 63 e this error occ 75 72 72 65 64 2c 0a 20 61 6e 64 20 74 68 65 20 urred,. and the 61 63 74 69 6f 6e 73 20 79 6f 75 20 70 65 72 66 actions you perf 6f 72 6d 65 64 20 6a 75 73 74 20 62 65 66 6f 72 ormed just befor 65 20 74 68 69 73 20 65 72 72 6f 72 2e 3c 2f 70 e this error..

More inform 61 74 69 6f 6e 20 61 62 6f 75 74 20 74 68 69 73 ation about this 20 65 72 72 6f 72 20 6d 61 79 20 62 65 20 61 76 error may be av 61 69 6c 61 62 6c 65 0a 69 6e 20 74 68 65 20 73 ailable.in the s 65 72 76 65 72 20 65 72 72 6f 72 20 6c 6f 67 2e erver error log. 3c 2f 70 3e 0a 3c 68 72 3e 0a 3c 61 64 64 72 65

. .Apache/2.4.7 28 55 62 75 6e 74 75 29 20 53 65 72 76 65 72 20 (Ubuntu) Server 61 74 20 77 73 2e 73 6c 61 74 6f 72 2e 69 6f 20 at ws.domain.io 50 6f 72 74 20 38 30 3c 2f 61 64 64 72 65 73 73 Port 80. 0a .
# T 104.131.x.x:80 -> 105.210.y.y:49991 [AF] # T 105.210.y.y:49991 -> 104.131.x.x:80 [A] 00 00 00 00 00 00 ......
# T 105.210.y.y:49991 -> 104.131.x.x:80 [A] 00 00 00 00 00 00 ......
# T 105.210.y.y:49983 -> 104.131.x.x:80 [AFP] 88 8a ad d9 9f c4 ae 30 cc ac d8 ad fb ab da b7 .......0........ # T 104.131.x.x:80 -> 105.210.y.y:49983 [A] # T 104.131.x.x:80 -> 105.210.y.y:49983 [AF] # T 105.210.y.y:49975 -> 104.131.x.x:80 [AR] 00 00 00 00 00 00 ......
# T 104.131.x.x:80 -> 105.210.y.y:49983 [AF] # T 105.210.y.y:49983 -> 104.131.x.x:80 [AFP] 88 8a ad d9 9f c4 ae 30 cc ac d8 ad fb ab da b7 .......0........ # T 104.131.x.x:80 -> 105.210.y.y:49983 [A] # T 105.210.y.y:49991 -> 104.131.x.x:80 [AF] 00 00 00 00 00 00 ......
# T 104.131.x.x:80 -> 105.210.y.y:49991 [A] # T 105.210.y.y:49991 -> 104.131.x.x:80 [AF] 00 00 00 00 00 00 ......
# T 104.131.x.x:80 -> 105.210.y.y:49991 [A] # T 105.210.y.y:49991 -> 104.131.x.x:80 [AF] 00 00 00 00 00 00 ......
# T 104.131.x.x:80 -> 105.210.y.y:49991 [A] # T 105.210.y.y:49991 -> 104.131.x.x:80 [AF] 00 00 00 00 00 00 ......
# T 104.131.x.x:80 -> 105.210.y.y:49991 [A] # T 104.131.x.x:80 -> 105.210.y.y:49983 [AF] # T 105.210.y.y:49991 -> 104.131.x.x:80 [AF] 00 00 00 00 00 00 ......
# T 104.131.x.x:80 -> 105.210.y.y:49991 [A] # T 105.210.y.y:49983 -> 104.131.x.x:80 [AR] 00 00 00 00 00 00 ......
# T 105.210.y.y:49991 -> 104.131.x.x:80 [AF] 00 00 00 00 00 00 ......
# T 104.131.x.x:80 -> 105.210.y.y:49991 [A] exit 83 received, 0 dropped

The ngrep output on port 8080 (between apache and tomcat)

  interface: lo (127.0.0.0/255.0.0.0)  filter: (ip or ip6) and ( port 8080 )  #  T 127.0.0.1:57952 -> 127.0.0.1:8080 [AP]    47 45 54 20 2f 74 72 61    6e 73 6c 61 74 6f 72 2d    GET /translator-    73 72 76 2f 77 73 20 48    54 54 50 2f 31 2e 31 0d    srv/ws HTTP/1.1.    0a 48 6f 73 74 3a 20 6c    6f 63 61 6c 68 6f 73 74    .Host: localhost    3a 38 30 38 30 0d 0a 53    65 63 2d 57 65 62 53 6f    :8080..Sec-WebSo    63 6b 65 74 2d 4b 65 79    3a 20 64 36 57 73 6c 6b    cket-Key: d6Wslk    56 48 77 79 4d 47 77 62    5a 4f 6c 71 56 53 2b 51    VHwyMGwbZOlqVS+Q    3d 3d 0d 0a 53 65 63 2d    57 65 62 53 6f 63 6b 65    ==..Sec-WebSocke    74 2d 56 65 72 73 69 6f    6e 3a 20 31 33 0d 0a 50    t-Version: 13..P    72 61 67 6d 61 3a 20 6e    6f 2d 63 61 63 68 65 0d    ragma: no-cache.    0a 43 61 63 68 65 2d 43    6f 6e 74 72 6f 6c 3a 20    .Cache-Control:     6e 6f 2d 63 61 63 68 65    0d 0a 58 2d 46 6f 72 77    no-cache..X-Forw    61 72 64 65 64 2d 46 6f    72 3a 20 31 30 35 2e 32    arded-For: 105.2    31 30 2e 33 38 2e 31 34    39 0d 0a 58 2d 46 6f 72    10.38.149..X-For    77 61 72 64 65 64 2d 48    6f 73 74 3a 20 77 73 2e    warded-Host: ws.    73 6c 61 74 6f 72 2e 69    6f 0d 0a 58 2d 46 6f 72    slator.io..X-For    77 61 72 64 65 64 2d 53    65 72 76 65 72 3a 20 77    warded-Server: w    73 2e 73 6c 61 74 6f 72    2e 69 6f 0d 0a 55 70 67    s.slator.io..Upg    72 61 64 65 3a 20 57 65    62 53 6f 63 6b 65 74 0d    rade: WebSocket.    0a 43 6f 6e 6e 65 63 74    69 6f 6e 3a 20 55 70 67    .Connection: Upg    72 61 64 65 0d 0a 0d 0a                               rade....
# T 127.0.0.1:8080 -> 127.0.0.1:57952 [R]

Lastly for completeness the jetty error

      org.eclipse.jetty.util.Utf8Appendable$NotUtf8Exception: Not valid UTF8! byte 88 in state 0   

"Windows Setup cannot find a location to store temporary installation files" when installing Server 2008 R2 on Server 2008

Posted: 11 Jun 2021 10:21 AM PDT

I'm trying to remotely install Windows Server 2008 R2 on a Server 2008 box using an iso image.

When I run the setup I get the error:

Install Windows

Windows Setup cannot find a location to store temporary installation files. To install Windows, make sure that a partition on your boot disk has at least 834 megabytes (MB) of free space.

Error code: 0x80070490

[OK]

There is plenty of space on both C: and D: and I've tried mounting the ISO (using Virtual Clone Drive) from both drives. I've also tried extracting the files from the ISO and running setup but I always get the same problem.

I thought the ISO file might be corrupt but I computed the SHA1 hash to be the same as the one listed on the MSDN download site.

If I had physical access to the machine I'd burn the ISO to a disk but I'm stuck with KVM remote access.

Any ideas?

Grant access rights to a MySQL instance based on hostname instead of IP address?

Posted: 11 Jun 2021 10:56 AM PDT

I have a MySQL database that I would like to remotely access from Windows Azure which does not provide fixed IP addresses at this point. Instead of white-listing a very large IP range to cover the entire Microsoft datacenter, it would be preferable to check for the hostname instead. Indeed, if I was allowing `myuser@'foo.example.com', DNS resolution being made when establishing a new connection to MySQL then varying IP address would not be an issue anymore.

Does anyone is such a scheme is possible with MySQL?

Chown operation not permitted for root

Posted: 11 Jun 2021 10:07 AM PDT

I try to chown the owner of a file to root, but I can't. I'm doing this as root. I get the following message:

chown: changing ownership of `ps': Operation not permitted  

No comments:

Post a Comment