I haven't done any work on my Joomla site in a while- no new changes. I just visited the home page and it returns this error. Any ideas on what this may be?
Fatal error: Uncaught exception 'InvalidArgumentException' with message 'Could not find template "yoo_avenue".' in /hermes/bosweb25b/b905/ipg.stokestackbbqcom/avenue/libraries/cms/application/site.php:510 Stack trace: #0 /hermes/bosweb25b/b905/ipg.stokestackbbqcom/avenue/libraries/legacy/error/error.php(778): JApplicationSite->getTemplate() #1 /hermes/bosweb25b/b905/ipg.stokestackbbqcom/avenue/plugins/system/redirect/redirect.php(130): JError::customErrorPage(Object(InvalidArgumentException)) #2 [internal function]: PlgSystemRedirect::handleError(Object(InvalidArgumentException)) #3 {main} thrown in /hermes/bosweb25b/b905/ipg.stokestackbbqcom/avenue/libraries/cms/application/site.php on line 510
Related
Is yaska supported in Linux? I tried installing it on CentOS and getting below error.
[root#390f68c98d2b yasca]# sh yasca.sh ./resources/test
Fatal error: Uncaught exception 'LogicException' with message 'Class Yasca\Scanner could not be loaded' in /var/www/html/yasca/Yasca/Main.php:36
Stack trace:
#0 /var/www/html/yasca/Yasca/Main.php(36): spl_autoload('Yasca\\Scanner')
#1 [internal function]: {closure}()
#2 /var/www/html/yasca/Yasca/Main.php(357): call_user_func(Object(Closure))
#3 /var/www/html/yasca/Yasca/Start.php(14): include('/var/www/html/y...')
#4 {main}
thrown in /var/www/html/yasca/Yasca/Main.php on line 36
Can someone please help in this?
I'm getting that error when trying to set up site on localhost
Fatal error: Uncaught exception 'PDOException' with message
'SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed:
No such host is known. ' in C:\xampp\htdocs\1\PHP Pro Bid
v7.6\library\Cube\Db\Adapter\PDO\Mysql.php:110 Stack trace: #0
C:\xampp\htdocs\1\PHP Pro Bid
v7.6\library\Cube\Db\Adapter\PDO\Mysql.php(110):
PDO->__construct('mysql:host=http...', 'ubidu_ge',
'AhJae!x5Gojetha...', Array) #1 C:\xampp\htdocs\1\PHP Pro Bid
v7.6\library\Cube\Db\Adapter\PDO\Mysql.php(135):
Cube\Db\Adapter\PDO\Mysql->_connect() #2 C:\xampp\htdocs\1\PHP Pro Bid
v7.6\module\Install\src\Install\Model\Parser.php(375):
Cube\Db\Adapter\PDO\Mysql->canConnect() #3 C:\xampp\htdocs\1\PHP Pro
Bid v7.6\module\Install\src\Install\Controller\Index.php(230):
Install\Model\Parser->parse(true) #4 C:\xampp\htdocs\1\PHP Pro Bid
v7.6\library\Cube\Controller\Dispatcher.php(131):
Install\Controller\Index->Index() #5 C:\xampp\htdocs\1\PHP Pro Bid
v7.6\library\Cube\Controller\Front.php(411):
Cube\Controller\Dispatcher->dispatch(Object(Cube\Controlle in
C:\xampp\htdocs\1\PHP Pro Bid
v7.6\library\Cube\Db\Adapter\PDO\Mysql.php on line 114
I upgraded from 1.9 to 1.9.1 via MagentoConnectManager. Everthing seems to work well and the site looks good. But the admin-page ist just a blank white page. I checked the .htaccess and the core_config_data table changed from http to https but nothing is working.
The exeption log shows (Links anonym):
xxxurlxxx ...app/Mage.php:595
Stack trace:
#0 xxxurlxxx ...app/code/core/Mage/Api/Model/Server.php(127): Mage::throwException('Invalid webserv...')
#1 xxxurlxxx ...api.php(78): Mage_Api_Model_Server->initialize(NULL)
#2 {main}
2015-02-28T00:31:47+00:00 ERR (3):
exception 'Mage_Core_Exception' with message 'Invalid webservice adapter specified.' in xxxurlxxx ...app/Mage.php:595
Stack trace:
#0 xxxurlxxx ...app/code/core/Mage/Api/Model/Server.php(127): Mage::throwException('Invalid webserv...')
#1 xxxurlxxx ...api.php(78): Mage_Api_Model_Server->initialize(NULL)
#2 {main}
2015-03-06T10:03:41+00:00 ERR (3):
exception 'Mage_Core_Exception' with message 'Invalid webservice adapter specified.' in xxxurlxxx ...app/Mage.php:595
Stack trace:
#0 xxxurlxxx ...app/code/core/Mage/Api/Model/Server.php(127): Mage::throwException('Invalid webserv...')
#1 xxxurlxxx ...api.php(78): Mage_Api_Model_Server->initialize(NULL)
#2 {main}
Can anybody please help and give me a hind what to do?
The page is h**p://....vinocada.de bye the way.
Best regards,
Markus
I have been searching and searching for any information regarding this redis error, but so far have not found any information. Any help would be greatly appreciated.
Here is my setup:
Laravel with 2 redis connections, 6379 for cache, and 6380 for a datastore.
Every couple of requests to the datastore, I get this error in my logs:
exception 'Predis\Protocol\ProtocolException' with message 'Unknown prefix: '1' [tcp://MY_SERVER_ADDRESS:6380]
This just started within the last few days, and I have not changed anything in the redis config or laravel redis config.
A little more info:
I do not have a prefix set in laravel anywhere.. laravel, predis, or redis is adding it itself.
The "prefix" that gets added changes, yesterday it was 'O', today it is '1'.
This is happening on two separate instances of laravel. The instances share an encryption key, but do not share any files or configs. They both connect to this redis server
Here is the full stack trace:
[2015-02-02 22:19:13] production.ERROR: exception 'Predis\Protocol\ProtocolException' with message 'Unknown prefix: '1' [tcp://MY_SERVER_ADDRESS:6380]' in /var/www/html/vendor/predis/predis/lib/Predis/Connection/AbstractConnection.php:151
Stack trace:
#0 /var/www/html/vendor/predis/predis/lib/Predis/Connection/StreamConnection.php(274): Predis\Connection\AbstractConnection->onProtocolError()
#1 /var/www/html/vendor/predis/predis/lib/Predis/Connection/StreamConnection.php(262): Predis\Connection\StreamConnection->read()
#2 /var/www/html/vendor/predis/predis/lib/Predis/Connection/AbstractConnection.php(130): Predis\Connection\StreamConnection->read()
#3 /var/www/html/vendor/predis/predis/lib/Predis/Connection/AbstractConnection.php(122): Predis\Connection\AbstractConnection->readResponse()
#4 /var/www/html/vendor/predis/predis/lib/Predis/Client.php(246): Predis\Connection\AbstractConnection->executeCommand()
#5 /var/www/html/vendor/predis/predis/lib/Predis/Client.php(228): Predis\Client->executeCommand()
#6 /var/www/html/app/interfaces/RedisRepository.php(47): Predis\Client->__call()
#7 /var/www/html/app/controllers/TrackingController.php(239): RedisRepository->registerNodeEventStatsGlobal()
#8 (): TrackingController->saveTrackerUserData()
#9 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(231): call_user_func_array()
#10 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(93): Illuminate\Routing\Controller->callAction()
#11 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(62): Illuminate\Routing\ControllerDispatcher->call()
#12 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(962): Illuminate\Routing\ControllerDispatcher->dispatch()
#13 (): {closure}()
#14 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Route.php(109): call_user_func_array()
#15 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(1028): Illuminate\Routing\Route->run()
#16 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(996): Illuminate\Routing\Router->dispatchToRoute()
#17 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(775): Illuminate\Routing\Router->dispatch()
#18 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(745): Illuminate\Foundation\Application->dispatch()
#19 /var/www/html/vendor/laravel/framework/src/Illuminate/Session/Middleware.php(72): Illuminate\Foundation\Application->handle()
#20 /var/www/html/vendor/laravel/framework/src/Illuminate/Cookie/Queue.php(47): Illuminate\Session\Middleware->handle()
#21 /var/www/html/vendor/laravel/framework/src/Illuminate/Cookie/Guard.php(51): Illuminate\Cookie\Queue->handle()
#22 /var/www/html/vendor/stack/builder/src/Stack/StackedHttpKernel.php(23): Illuminate\Cookie\Guard->handle()
#23 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(641): Stack\StackedHttpKernel->handle()
#24 /var/www/html/public/index.php(49): Illuminate\Foundation\Application->run()
#25 {main} [] []
Help plz :(
The issue turned out to be specific to HHVM. Once I switched back to PHP-FPM the errors stopped.
HHVM does still have its quirks.
I am trying to program a simple FTPS server based on EventMachine.
Control socket works properly. When using data socket for data transfer, it seems that everything works well (TLS handshake completes successfully and data is received), but then I get an error message. Here is what I get in Filezilla:
Command: LIST
Response: 150 Opening ASCII mode data connection for file list
Trace: CFtpControlSocket::TransferParseResponse()
Trace: code = 1
Trace: state = 4
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Trace: state = 5
Trace: CTransferSocket::OnConnect
Trace: CTlsSocket::Handshake()
Trace: gnutls_session_get_data on primary socket failed: -51
Trace: CTlsSocket::ContinueHandshake()
Trace: CTlsSocket::OnSend()
Trace: CTlsSocket::OnSend()
Trace: CTlsSocket::OnRead()
Trace: CTlsSocket::ContinueHandshake()
Trace: CTlsSocket::OnRead()
Trace: CTlsSocket::ContinueHandshake()
Trace: Handshake successful
Trace: Cipher: AES-256-CBC, MAC: SHA1
Trace: CTlsSocket::OnRead()
Trace: CTransferSocket::OnConnect
Trace: CTransferSocket::OnReceive(), m_transferMode=0
Listing: -rwxrwxrwx 1 owner group 1011 Dec 12 23:05 a.tmp
Trace: CTlsSocket::Failure(-9, 0)
Error: GnuTLS error -9: A TLS packet with unexpected length was received.
Status: Server did not properly shut down TLS connection
Error: Could not read from transfer socket: ECONNABORTED - Connection aborted
Trace: CTransferSocket::TransferEnd(3)
Trace: CFtpControlSocket::OnReceive()
Response: 226 Closing data connection, sent 70 bytes
Trace: CFtpControlSocket::TransferParseResponse()
Trace: code = 2
Trace: state = 5
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::TransferSend()
Trace: state = 8
Trace: CFtpControlSocket::TransferEnd()
Trace: CFtpControlSocket::ResetOperation(2)
Trace: CControlSocket::ResetOperation(2)
Trace: CFtpControlSocket::ParseSubcommandResult(2)
Trace: CFtpControlSocket::ListSubcommandResult()
Trace: state = 3
Trace: CFtpControlSocket::ResetOperation(2)
Trace: CControlSocket::ResetOperation(2)
Error: Failed to retrieve directory listing
Trace: CFileZillaEnginePrivate::ResetOperation(2)
ftp-ssl also issues an error although somewhat different
--> LIST
150 Opening ASCII mode data connection for file list
===>START SSL connect on DATA
ftp: SSL_connect DATA error 0 - error:00000000:lib(0):func(0):reason(0)
226 Closing data connection, sent 70 bytes
421 Service not available, remote server has closed connection
From what I found on the web I suspect this behavior is because close_notify is not issued at the end of connection? If so, is there any known Ruby based solution for that (f.ex. using OpenSSL::SSL::SSLSocket)?
Answer is quite short: no, EventMachine doesn't issue close_notify on close_connection if tls_start was run.
I found SSL 're-opens' a connection after reading the cert, so work around here is:
def receive_data bitOfData
if (self.class isSomeSortOfTLSreadingClass && bitOfData.length == 1) then
#headBuff << bitOfData
return
end
# TLS connection closes on first byte, then re-opens.
end