error code pid

[Donna]

Can you help me with understanding these code errors:

They all start with a PID

I don’t know how to tell if the deactivation and changing of themes did anything to these error messages or stopped any conflict.

Here is an example. Your system will not allow me to upload the .txt file and I am not sure what else it will accept. [Thu Aug 25 15:04:28.174356 2016] [:error] [pid 2238] [client 51.254.97.218:55212] event-tickets/common – Log: Initializing

Tribe Events on Aug, 25th at 03:08:28 pm
[Thu Aug 25 15:04:30.974169 2016] [:error] [pid 15817] [client 51.254.97.218:55228]

event-tickets/common – Log: Initializing Tribe Events on Aug, 25th at 03:08:30 pm
[Thu Aug 25 15:04:34.403293 2016] [:error]

[pid 869] [client 51.254.97.218:55239] event-tickets/common – Log: Initializing Tribe Events on Aug, 25th at 03:08:34 pm
[Thu Aug 25 15:04:37.792359 2016] [:error] [pid 14893] [client 51.254.97.218:55245] event-tickets/common – Log:

Initializing Tribe Events on Aug, 25th at 03:08:37 pm
[Thu Aug 25 15:04:41.332411 2016] [:error] [pid 16937] [client

51.254.97.218:55255] event-tickets/common – Log: Initializing Tribe Events on Aug, 25th at 03:08:41 pm
[Thu Aug 25

15:04:46.786137 2016] [:error] [pid 15817] [client 51.254.97.218:55263] event-tickets/common – Log: Initializing Tribe

Events on Aug, 25th at 03:08:46 pm
[Thu Aug 25 15:04:49.576194 2016] [:error] [pid 14893] [client 51.254.97.218:55271]

event-tickets/common – Log: Initializing Tribe Events on Aug, 25th at 03:08:49 pm
[Thu Aug 25 15:04:53.238535 2016] [:error]

[pid 16937] [client 157.55.39.100:55290] event-tickets/common – Log: Initializing Tribe Events on Aug, 25th at 03:08:53 pm
[Thu Aug 25 15:04:58.844674 2016] [:error] [pid 2223]

[Brook]

Howdy Donna,

Welcome to the forums! It would be my pleasure to assist with this.

“pid” stands for Process ID in this case. You can basically ignore that portion of the message. The one thing that is consistent though is this:

event-tickets/common – Log: Initializing Tribe

The log you are looking at super generic, and not usually helpful in this sort of situation. Sometimes lines like the above are more faux errors, and not indications of any real problem. Sometimes they do indicate problems tho, so it is certainly worth investigating further.

Are you experiencing any bad behavior on the site around the time of these error messages? If so what?

Does your server have PHP error logs? If so those will contain a lot more detail on what is happening. If not you might enabled WP_DEBUG and WP_DEBUG_LOG, which will create a debug.log file in your WordPress install. From there wait a little bit and check the file to see if there are any PHP errors in it. More details can be found in that wp debug link above. If you are seeing some actual PHP error messages in any of these logs, what are they?

Cheers!

– Brook

[Donna]

Thanks Brook. For some reason the debug log stopped in July.
I did have some funky things going on at the time. For some reason I had 595 abandoned carts show up in a span of half an hour. I discovered these errors trying to figure out what the problem is.

Most of the php errors have to do with recapcha. I changed to the google plugin a few weeks ago because of users telling me they were having issues with it.

does that help?

Thanks again.

[Brook]

Howdy again!

For some reason the debug log stopped in July.

If you have been running the wp debug log for a while, it is possible the log has gotten too big. You might try downloading the current copy of it then deleting it.

Most of the php errors have to do with recapcha. I changed to the google plugin a few weeks ago because of users telling me they were having issues with it.

I am not sure what you are referring to here. What is the recaptcha plugin for? Does it protect your login form, contact form? Which plugin are you using?

Probably the only way to get to the bottom of what is happening will be to see the PHP errors themselves. The abandoned carts are certainly alarming, but I have no idea what could have temporarily caused those without seeing any error messages. For all we know your server was under DDOS or some other arbitrary temporary issue that would be impossible to know without proper documentation. It’s entirely possible that whatever caused the error will never resurface again, along with all the other possibilities. At this point there are too many unknown to jump to conclusions. If you can get a log going that would be super helpful. 🙂

Cheers!

– Brook

[Donna]

Thanks Brook. I don’t know what DDOS means. I have asked for help from several places and everyone seems puzzled by why and how it happened. It could just be one of those things.

The only “PHP” error messages seem to be related to a plugin that I am not using any more.

Seen here: PHP Notice: map_meta_cap was called incorrectly. The post type u_course is not registered, so it may not be reliable to check the capability “read_post” against a post of that type. Please see Debugging in WordPress for more information. (This message was added in version 4.4.0.) in /nas/content/live/bixbee/wp-includes/functions.php on line 3897
[29-Aug-2016 19:49:50 UTC] PHP Notice: map_meta_cap was called incorrectly. The post type u_course is not registered, so it may not be reliable to check the capability “edit_post” against a post of that type. Please see Debugging in WordPress for more information. (This message was added in version 4.4.0.) in /nas/content/live/bixbee/wp-includes/functions.php on line 3897
[29-Aug-2016 19:49:56 UTC] event-tickets/common – Log: Initializing Tribe Events on Aug, 29th at 07:08:56 pm
[29-Aug-2016 19:50:03 UTC] event-tickets/common – Log: Initializing Tribe Events on Aug, 29th at 07:08:03 pm
[29-Aug-2016 19:50:24 UTC] event-tickets/common – Log: Initializing Tribe Events on Aug, 29th at 07:08:24 pm

I appreciate all your efforts.

[Brook]

You are so welcome.

No worries about not knowing what a DDOS is. It was just an example of something which causes errors but only temporarily, and is unlikely to ever impact your site again. There are many things that can do this. Hence why I wanted to learn more before jumping to conclusions.

Have you deactivated and uninstalled that plugin, or is it still active on your site but unused? Uninstalling it might cause that error to stop appearing in the future. However, many times plugins leave behind a few remnants here and there even when uninstalled. So that is Notice you might continue seeing. The notice itself is harmless. Notices are intended for plugin/theme developers, most of the time a site owner like yourself can safely ignore them. The Notice you have shared is a classic example of something that can be safely ignored.

The good news here is that so far there are no real errors on your site. Nothing about your site is actually broken according to the logs. Worth keeping an eye on them for a little while longer though to see if something significant pops up.

Cheers!

-Brook

[Donna]

Thank you Brook for easing my mind. It seems it was a fluke and none of the developers I know can find it either. Thanks again for your time.

[Brook]

You are so very welcome! Just to error on the side of caution I’ll leave this thread open another couple weeks. If you notice more errors I’ll be here to review them.

Cheers!

– Brook

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts