PHP error_log is not logging 500 errors

Windows Server 2016, IIS, PHP 5.6.31

I’ve temporarily set my error_report to E_ALL, and I’ve restarted my web server in IIS, to help me figure out why I’m getting a 500 error.

error_reporting = E_ALL

Unfortunately I’m still not getting any info in my error_log regarding this error. I do get other errors and warnings logged, but nothing for this 500 error. Is PHP not supposed to log some details for me? Why am I not seeing any error details?

linux – How can I debug an intermittent server crash that rejects SSH connections, causes I/O errors, and renders existing sessions useless?

I’ve been running a home server based on debian for ~10 years now and recently decided to replace it with an HP EliteDesk 705 65W G4 Desktop Mini PC, but the new machine keeps crashing.

The machine will run fine for a few hours, then suddenly begins:

  1. Rejecting SSH connections immediately
  2. Returning “Command not found” for any commands run in existing ssh connections (e.g., ls)
  3. Giving I/O errors in response to running processes like docker stats
  4. Not showing any display output to connected monitors

I typically run a few home services in docker containers and initially thought an oddity of my config might be causing the crashes, so I decided to select a random existing github repo with a few containers and run it from scratch. I decided to use this HTPC download box repo, which seems to have a few linuxserver.io containers and should be a reasonable approximation for the lower bound of the workload my services would put on the machine.

Steps I have followed to create the crash:

  1. Install headless debian (netinstall image); configure the OS by following the below steps:
  2. Set hostname: test
  3. Set domain: example.com
  4. Add a new user, add user to sudoers, set up SSH to allow for only keys and only nick can log in (including adding my desktop’s public key to ~/.ssh/authorized_keys)
adduser nick
usermod -aG sudo nick
sudo nano /etc/ssh/sshd_config; the specific settings you want are:
PermitRootLogin no
Protocol 2
MaxAuthTries 3
PubkeyAuthentication yes
PasswordAuthentication no
PermitEmptyPasswords no
ChallengeResponseAuthentication no
UsePAM no
AllowUsers nick
  1. Restart ssh: sudo service sshd restart
  2. Install necessary services: sudo apt-get install docker docker-compose git
  3. Add your user to the docker group: sudo usermod -aG docker nick
  4. Generate a new ssh key and add it to your GitHub account: ssh-keygen -t ed25519, then copy the public key to GH
  5. Set your global git vars: git config --global user.name 'Nick'; git config --global user.email nick@example.com

Wait 2 days, verify no crash occurs

  1. Run the following commands:
cd /opt
sudo mkdir htpc-download-box
sudo chown -R nick:nick htpc-download-box
git clone git@github.com:sebgl/htpc-download-box.git
cd htpc-download-box
docker-compose up -d

(Note: I do no configuration whatsoever of the containers in the docker-compose file, I just start them running and then confirm I can access them via browser. I use the exact .env.example as the .env for the project.)

Wait a few hours, observe that server has crashed. Unable to log in via SSH and other issues as stated above. Interestingly, I can still view the web UI of some containers (e.g., sonarr) but when trying to browse the filesystem via that web UI, I am unable to see any folders and manually typing the path indicates that the user has no permissions to view that folder.

Since I observe crashes when running either my actual suite of services or the example repo detailed here, I must conclude it’s an issue with the machine itself. I have tested the nvme drive with smartmontools and both the short and long tests report no errors.

I am not familiar enough with Linux to know how to proceed from here (maybe give it another 10 years!) – what logs can I examine to determine what might cause the crash? Should I be setting up additional logging of some sort to try to ascertain the cause?

All of the issues are so general (I/O errors, SSH refusal, etc.) that Googling for the past week has not gotten me anywhere; I was sure the clean reinstall and using a new repo would not crash and I could then incrementally add my actual docker containers until a crash occurred, therefore finding the problematic container via trial and error, but I am now at a complete loss for how to proceed.

rac – DNS/NIS name service : Errors while installing Oracle Grid Infra 12c

Team:

I am installing Grid infra 12cR1 with SCAN entries added to /etc/hosts (I am aware this is not the preferred mechanism per Doc ID 887471.1. This is for a practice instance) as follows:

# SCAN (in production this should be configured in DNS)
192.168.56.91 srv-scan.localdomain srv-scan
192.168.56.92 srv-scan.localdomain srv-scan
192.168.56.93 srv-scan.localdomain srv-scan

Guest OS: OEL7

Virtual-box: 6.1

Host OS: Win-10

While installing the grid software, I am seeing the below error:


DNS/NIS name service - This test verifies that the Name Service lookups for the Distributed Name Server (DNS) and the Network Information Service (NIS) match for the SCAN name entries.  Error: 
 - 
PRVG-1101 : SCAN name "srv-scan" failed to resolve  - Cause:  An attempt to resolve specified SCAN name to a list of IP addresses failed because SCAN could not be resolved in DNS or GNS using ''nslookup''.  - Action:  Check whether the specified SCAN name is correct. If SCAN name should be resolved in DNS, check the configuration of SCAN name in DNS. If it should be resolved in GNS make sure that GNS resource is online. 
 - 
PRVF-4657 : Name resolution setup check for "srv-scan" (IP address: 192.168.56.91) failed  - Cause:  Inconsistent IP address definitions found for the SCAN name identified using DNS and configured name resolution mechanism(s).  - Action:  Look up the SCAN name with nslookup, and make sure the returned IP addresses are consistent with those defined in NIS and /etc/hosts as configured in /etc/nsswitch.conf by reconfiguring the latter. Check the Name Service Cache Daemon (/usr/sbin/nscd) by clearing its cache and restarting it. 
 - 
PRVF-4657 : Name resolution setup check for "srv-scan" (IP address: 192.168.56.92) failed  - Cause:  Inconsistent IP address definitions found for the SCAN name identified using DNS and configured name resolution mechanism(s).  - Action:  Look up the SCAN name with nslookup, and make sure the returned IP addresses are consistent with those defined in NIS and /etc/hosts as configured in /etc/nsswitch.conf by reconfiguring the latter. Check the Name Service Cache Daemon (/usr/sbin/nscd) by clearing its cache and restarting it. 
 - 
PRVF-4657 : Name resolution setup check for "srv-scan" (IP address: 192.168.56.93) failed  - Cause:  Inconsistent IP address definitions found for the SCAN name identified using DNS and configured name resolution mechanism(s).  - Action:  Look up the SCAN name with nslookup, and make sure the returned IP addresses are consistent with those defined in NIS and /etc/hosts as configured in /etc/nsswitch.conf by reconfiguring the latter. Check the Name Service Cache Daemon (/usr/sbin/nscd) by clearing its cache and restarting it. 

  Check Failed on Nodes: (srv1,  srv3)  
Verification result of failed node: srv1  Details: 
 - 
PRVF-4664 : Found inconsistent name resolution entries for SCAN name "srv-scan"  - Cause:  The nslookup utility and the configured name resolution mechanisms, as defined in /etc/nsswitch.conf, returned inconsistent IP address information for the SCAN name identified.  - Action:  Check the Name Service Cache Daemon (/usr/sbin/nscd), the Domain Name Server (nslookup) and the /etc/hosts file to make sure the IP address for the SCAN names is registered correctly. Clear the stale IP addresses from the name service cache using the command ''/usr/sbin/nscd -i hosts''. 
Back to Top  
Verification result of failed node: srv3  Details: 
 - 
PRVF-4664 : Found inconsistent name resolution entries for SCAN name "srv-scan"  - Cause:  The nslookup utility and the configured name resolution mechanisms, as defined in /etc/nsswitch.conf, returned inconsistent IP address information for the SCAN name identified.  - Action:  Check the Name Service Cache Daemon (/usr/sbin/nscd), the Domain Name Server (nslookup) and the /etc/hosts file to make sure the IP address for the SCAN names is registered correctly. Clear the stale IP addresses from the name service cache using the command ''/usr/sbin/nscd -i hosts''. 
Back to Top  

Can I ignore this error because am not using DNS and proceed with the installation?

ssl certificate errors – Unable to open file for reading: /etc/exim/domains on Centos 7 – err_ssl_protocol_error

How can I fix the issue below I saw at /var/log/messages

panel crond: 2020-11-13 21:17:02 1kdgRJ-0008yG-Rv Tainted filename ‘/etc/exim/domains/example.com/dkim.pem’
panel crond: 2020-11-13 21:17:02 1kdgRJ-0008yG-Rv unable to open file for reading: /etc/exim/domains/example.com/dkim.pem

The actual permissions are:
drwxr-xr-x 2 root root 164 Nov 12 19:45 /etc/exim/domains
drwxrwx–x 2 exim mail 100 Nov 12 19:45 /etc/exim/domains/example.com/
-rw-rw—- 1 exim mail 887 Nov 12 19:45 /etc/exim/domains/example.com/dkim.pem

My sites are not loading, and show an err_ssl_protocol_error, or eror_connection_closed, or ssl handshake failed error 525

magento2.3.5 p2 – Fotorama Gallery JS Errors With Magepack JS Bundling Enabled

We are using Magepack on a Magento v2.3.5-p2 website for JS bundling. See below:

https://github.com/magesuite/magepack

If we enable magepack JS bundling using the Luma or Blank theme it works fine without issue. However when we enable this using the clients implementation of porto theme it breaks the fotorama image gallery on the product pages. See error message that appears in the JS console below:

Uncaught TypeError: settings.$elementF.fotorama is not a function

When magepack JS bundling is disabled the image gallery works fine. It also works fine if the core Magento JS bundling is enabled. The issue is isolated to when magepack is enabled as far as we can tell.

Does anyone have any experience of this same issue when using Magepack JS bundling?
Does anyone know how to debug issues like this?
Is it something simple thing that we are missing like reordering the files in the magepack.config.js file?

I will fix wordpress issues, fix wordpress errors and bugs quickly for $20

I will fix wordpress issues, fix wordpress errors and bugs quickly

★ Best WordPress Bug Fixer with over 7+ Years Experience There is absolutely nothing that I can’t fix in WordPress.◉ My Services include but Limited to : Fix WordPress errors


Error Establishing Database Connection

Fixing Plugin issues

White Screen of Death


Fixing WordPress theme CSS issues

Customization of theme

Fatal Errors

Responsive layout issues,

Slider Revolution Issue


Woocommerce Plugin Issue

◉ Configuration of theme or plugins◉ CSS and responsive design issues◉ Updates, Speed and Security◉ Database issues◉ Theme customizations◉ Broken layout.. and so on..◉ SSL – HTTPSWhy Hire Me?

  • 7 Year Professional Development Experience
  • Professional Service at Lowest Cost
  • Full Support and Consultancy.
  • Faster Turn Around
  • 24 hours express delivery
  • 100% money-back guarantee

** 100% positive rating **
If you have more than one problem, feel free to inbox and discuss that in detail.Thank you and I look forward to the opportunity to work with you.

.

filesystem – Errors in initramfs-tools

I’ve been having an error when updating or running any apt command for a week or so. Upgrading to LTS 18.04 hasn’t resolved it, nor has removing all old kernels. Space isn’t an issue either.

Attempting to reinstall initramfs doesn’t work. Error I get is:

Setting up initramfs-tools (0.136ubuntu6.3) …
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.136ubuntu6.3) …
update-initramfs: Generating /boot/initrd.img-5.4.0-52-generic
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.4.0-52-generic with 1.
dpkg: error processing package initramfs-tools (–configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:

Magento2 PayPal NVP gateway errors: The totals of the cart item amounts do not match order amounts

My base currency is U.S. dollar (USD)., when I go to PayPal express checkout, everything is working fine I can checkout in USD. But when I use Canadian Dollars (CAD) in PayPal express checkout,it is not working.

My magento version is magento 2.2.Please help me, thanks.