CPanel - Error login “A fatal error or timeout occurred while processing this directive. ” - server

I face this problem multiple time. It happen when I put my login information on cpanel login, then the page goes empty except these message:
Template::Exception:
[TYPE]=[file]
[INFO]=[parse error - home/retro/stats_bar.html.tt line 84-90: unexpected token (%)
[% IF stat.pc.defined;
stat.percent = stat.pc;
[%
IF stat.pc.defined;
stat.percent = stat.pc;
END; %]]
[TEXT]=[
]
at cpanel.pl line 1050.
cpanel::cpanel::cptt_exectag("/usr/local/cpanel/base/frontend/paper_lantern/index.auto.tmpl", 1) called at cpanel.pl line 4408
cpanel::cpanel::run_standard_mode() called at cpanel.pl line 864
cpanel::cpanel::script("cpanel::cpanel", "./frontend/paper_lantern/index.html") called at cpanel.pl line 271
I tried to re-install the cpanel by using this command scripts/upcp --force it goes good. But the next day happen again, at the exact time of 11:30 am.
I opened CPanel support ticket, but it has been a day, and no reply yet.

Hello,
If you running just cpanel, do cpanel force update
"/scripts/upcp --force"
If you running cpanel with CloudLinux do LVE Manager updated
"yum update lvemanager"
Visit https://www.cloudlinux.com/cloudlinux-os-blog/entry/lve-manager-updated-1-6
lvemanager-2.0-41 1
WEB-689: set Content-type: text/html in CloudLinux.cgi;
WEB-839: fixed broken cPanel's styles when "LVE Manager" plugin is opened (cPanel 11.69.9999 only);
LVEMAN-1203: fixed retro theme errors on cPanel EDGE (11.70);
LVEMAN-1188: improved StatsBar integration in cPanel WHM.

Related

Moodle 2.6 mailer not working properly

I'm having trouble with moodle mailer , problem is that moodle is not sending mail after registration to student and when somebody click forgotten password mail doesnt come to user also.
Error logs are empty
I tried to change to send via smtp servers but is not working
My moodle version is 2.6.1 and i cannot upgrade to higher version.
Can somebody please help me with this trouble ?
This is error log:
Error code: filenotfound
* line 463 of /lib/setuplib.php: moodle_exception thrown
* line 1948 of /lib/filelib.php: call to print_error()
* line 1201 of /lib/outputlib.php: call to send_file_not_found()
* line 94 of /theme/essential/lib.php: call to theme_config->setting_file_serve()
* line 4628 of /lib/filelib.php: call to theme_essential_pluginfile()
* line 37 of /pluginfile.php: call to file_pluginfile()
Edit your config.php and enter this
$CFG->debugsmtp = true;
Or go to site admin -> development -> debugging -> and check 'Debug email sending'
It will show verbose messages when sending email so might show what's wrong.
Alternatively, use an editor with xdebug enabled (I use Netbeans IDE) - then add a breakpoint at the start of the function email_to_user() in /lib/moodlelib.php - Then step through until it fails.
Problem Solved
I had to set port in lib/moodlelib.php to 465 (My provider want me to use 587)

cli showing unknown sip registration in asterisk

I am using asterisk 11.9.0 everything works fine but cli shows unknown sip registrations with my current code running
my cli output
-- Hungup 'DAHDI/i1/9560790782-2fd2'
[Jun 24 14:55:24] NOTICE[3637]: chan_sip.c:25757 handle_request_register: Registration from '"4001" <sip:4001#182.74.197.19:5060>' failed for '37.8.47.82:22939' - Wrong password
[Jun 24 14:55:25] NOTICE[3637]: chan_sip.c:25757 handle_request_register: Registration from '"3822" <sip:3822#182.74.197.19:5060>' failed for '37.8.47.82:23187' - Wrong password
[Jun 24 14:55:29] NOTICE[3637]: chan_sip.c:25757 handle_request_register: Registration from '"5555" <sip:5555#182.74.197.19:5060>' failed for '37.8.47.82:22848' - Wrong password
how can i remove this because my dialplan is taking too much time to execute as compared to the past.
Any help would be appreciated.
Very likly that is automated programs(bots) with goal find your secrets/on success call out to Cuba or other costly destinations.
Every asterisk installation need have at least rate limiter - usually fail2ban.org used. That will prevent bots from spamming too fast.

in wordpress, a valid callback for cp_admin_init and _canonical_charset

I'm using WordPress 3.5 with child-theme of Twenty Eleven 1.5. Suddenly I'm getting following Warning,
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'cp_admin_init' was given in /home/templ/public_html/wp-includes/plugin.php on line 406
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, '_canonical_charset' was given in /home/templ/public_html/wp-includes/plugin.php on line 173
I'm using following plugins:
download-manager 2.3.9
wordpress-seo 1.4.7
wp-pagenavi 2.83
Some more points:
1) If I'm giving mysite.com it's giving above 2 line warning. If I give www.mysite.com, the following line also include,
Warning: Cannot modify header information - headers already sent by (output started at /home/templ/public_html/wp-includes/plugin.php:406) in /home/templ/public_html/wp-includes/pluggable.php on line 876
2) If I give mysite.com/wp-admin/ or www.mysite.com/wp-admin/, It's giving 1st warning and 3rd warning.
3) If I goto www.mysite.com/wp-login.php, It's giving following 5 warning.
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'cp_admin_init' was given in /home/templ/public_html/wp-includes/plugin.php on line 406
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, '_canonical_charset' was given in /home/templ/public_html/wp-includes/plugin.php on line 173
Warning: Cannot modify header information - headers already sent by (output started at /home/templ/public_html/wp-includes/plugin.php:406) in /home/templ/public_html/wp-login.php on line 368
Warning: Cannot modify header information - headers already sent by (output started at /home/templ/public_html/wp-includes/plugin.php:406) in /home/templ/public_html/wp-login.php on line 380
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'wp_authenticate_spam_check' was given in /home/templ/public_html/wp-includes/plugin.php on line 173
4) If I give correct username and password, it's not going to login. giving following problem,
ERROR: Invalid username or incorrect password.
ERROR: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.
I'm trying to find solution. I can't. Can any-one help me?
This sounds like a corrupted install. So you have a few options to fix this:
Attempt to get logins operational again and doing an upgrade though the wp-admin: Explained Below.
Do a manual Update: http://codex.wordpress.org/Updating_WordPress#Manual_Update
But First: Make a Backup
Please be sure to backup your install! Before proceeding: http://codex.wordpress.org/WordPress_Backups
Getting Logins Working: Masking the symptoms
First I would disable debugging output because that should fix most of these issues. When a warning occurs in Wordpress, PHP starts writing the response body and closes the header section of the response. This means that whenever Wordpress tries to add another header after the original warning was raised, PHP will raise another warning:
Warning: Cannot modify header information - headers already sent by (output started at /home/templ/public_html/wp-includes/plugin.php:406) in /home/templ/public_html/wp-login.php on line 380
So if we disable debugging then we should be able to mask the symptoms. This is a quick patch for a larger problem that we will have to solve with an in-place upgrade
To Disable Debugging
Ensure that the following constants exist and are set correctly is in your wp-config.php file
define('WP_DEBUG', false);
and
define('WP_DEBUG_DISPLAY', false);
Now you should be able to login to your site as an administrator without errors.
Disable your Plugins
Disable all your plugins in Plugins -> Installed Plugins This is imperative so that we can make sure that the update goes smoothly.
Do an Update
Go to Dashboard -> Updates and click either Update Now or Re-install Now
Reactivate your Plugins
Reactivate all your plugins in Plugins -> Installed Plugins and update them if necessary.
That's It
That's the process for reinstalling Wordpress. The key here is that you have Debugging enabled on a production site which is not good. You should always have WP_DEBUG and WP_DEBUG_DISPLAY set to false in a production environment.

Warning: curl_setopt() [function.curl-setopt]: Invalid curl configuration option in facebook_base.php

A week ago I started to notice a problem with the php sdk file - facebook_base.php
sometimes when connected facebook member visit the site and the auto-login trigger I get 2 errors and sometimes only the first error (that is why I used it in my problem title)+ the site shows up but without showing that user is connected.
after a refresh no error is shown and the site for connected member shows up.
I've tried new version of php API and also old ones that worked and still problem remained.
any ideas what can cause the problem?
UPDATE: similar problem spotted here: https://developers.facebook.com/bugs/207087046099691?browse=search_512a0e37e7ecf6136191651
this is the errors:
Warning: curl_setopt() [function.curl-setopt]: Invalid curl configuration option in /home/admin/domains/mydomain.com/public_html/includes/base_facebook.php on line 970
Warning: curl_setopt_array() [function.curl-setopt-array]: Array keys must be CURLOPT constants or equivalent integer values in /home/admin/domains/mydomain.com/public_html/includes/base_facebook.php on line 946

TYPO3 - PHP errors after server restart

We had to restart a server that has a TYPO3 site on it. We made no changes to the database of any of the TYPO3 files themselves, just a standard restart. The issue is that now the server is spewing php errors. I would like to stress that no server configuration changes were made.
A sample of our error logs:
[Wed Jun 27 23:55:19 2012] [error] [client ****************] PHP Strict Standards:
Declaration of tx_commerce_db_article::get_attributes() should be compatible with tx_commerce_db_alib::get_attributes($uid, $attribute_corelation_type_list = '')
in /var/www/html/***********/class.tx_commerce_db_article.php on line 63
Anyone have any ideas of what might have cause typ03 to make a deposit on the living room rug?
The server will take the request but admin page and main page will not display.
Someone updated PHP to version 5.4 on the server. Only the latest dev versions in the git repositories include a fix to the display error pattern that explicitly excludes E_STRICT.
Have a look at this issue and the according patches:
http://forge.typo3.org/issues/35154