No, it's not normal. Ideally all error log(s) should be empty. You have to look at each reported error and decide if it's something you can do something about. For example, are you getting 404 errors? Those that are due to not having your own "error documents" (e.g., missing /500.shtml) can be cured by defining a set of commonly-needed error documents (error handlers, error pages). cPanel has a button to define the core of /400.shtml, 401, 403, 404, and 500 -- I don't know what LPCP has. Are other 404s due to bad internal links in your pages (links to missing pages, misspelled links, etc.)?  Fix them! Are some due to other sites/users/search engines referring to pages that you've changed/moved/removed? Use 301 redirects to send such requests to an existing page.  404 errors that don't fit any of the above categories may be hacking attempts (looking for common exploits in canned applications). Ban the IP addresses making the requests. Are you getting 500 errors? They indicate a problem with one or more files. Some error logs list PHP code errors -- fix them. Etc., etc. This link lists a number of things which cause error log entries, and what can be done about them. Keep an eye on your error logs, and keep dealing with errors that pop up. If your site is Joomla-based, see what tools they offer for dealing with Joomla-specific errors (does it have its own error log)? SMF has its own error log that reports certain coding errors (e.g., undefined indexes) as well as the usual trash of incorrect password attempts, etc.).

In some cases, Joomla (or another application) may offer tools to deal with some specific errors, but most often you are going to have to do some digging to find out what happened, and to fix whatever is causing the problem. All part of running a website!