HelloW!
When I went to upgrade moodle 3.10 to 3.11 and later 4.x.
I got a problem, after installing all the plugins that weren't on disk, and others that weren't found.
When proceeding, I had this image error.
Error Image Print
I use moodle in PT-BR, this is an error log:
Atualizando para nova versão
Importação de idioma: pt_br_old
Impossível achar componente
Outras informações sobre este erro
Informações de depuração: pt_br_old
Error code: cannotfindcomponent×Ignorar essa notificação
Rastreamento de pilha:
line 810 of /lib/componentlib.class.php: lang_installer_exception thrown
line 665 of /lib/componentlib.class.php: call to lang_installer->install_language_pack()
line 45 of /admin/tool/langimport/lib.php: call to lang_installer->run()
line 1741 of /lib/upgradelib.php: call to tool_langimport_preupgrade_update()
line 1856 of /lib/upgradelib.php: call to upgrade_language_pack()
line 519 of /admin/index.php: call to upgrade_core()
log in english:
Updating to new version
Language import: pt_br_old
Impossible to find component
Other information about this error
Debug info: pt_br_old
Error code: cannotfindcomponent×Ignore this notification
Stack tracking:
line 810 of /lib/componentlib.class.php: lang_installer_exception thrown
line 665 of /lib/componentlib.class.php: call to lang_installer->install_language_pack()
line 45 of /admin/tool/langimport/lib.php: call to lang_installer->run()
line 1741 of /lib/upgradelib.php: call to tool_langimport_preupgrade_update()
line 1856 of /lib/upgradelib.php: call to upgrade_language_pack()
line 519 of /admin/index.php: call to upgrade_core()
I installed all the missing plugins on the disk given in the update.
I downloaded and installed the PT-BR Moodle 3.11 language pack in the lang folder and also cleared the cache of the folders inside moodledata in my case it has another name. But i don't delete lang folder in moodledata and exist content in this folder.
path moodledata: /var/AnotherName
I updated the system, ubuntu, entered the permissions in the folder again and nothing worked until now.
I kept the config.php from the old moodle as recommended. The only warning I got in the update was about input_vars below 5000, and about the database not being in exact moodle format. But it was just warnings.
Related
I get the following error message when executing jcmd 115 JFR.dump name=continuous_recording:
115:
Dump failed. No data found in the specified interval.
I started the recording with the following configuration:
XX:StartFlightRecording=disk=true,dumponexit=true,
filename=/home/site/diagnostics/recording.jfr,
maxsize=1024m,maxage=1d,name=continuous_recording
It could be that the buffer has not yet filled the minimum chunk size. But the JFR.check command does not provide that information.
Update:
I can get a dump from the Java app if I run JFR.dump without specifying the name of the recording. I tried encapsulating the recording name with quotes (escaped and un-escaped) and got the same error as before.
005c736ce3ee:/home# jcmd 115 JFR.dump filename="home/6_10_dump1.jfr"
Picked up JAVA_TOOL_OPTIONS: -Djava.net.preferIPv4Stack=true
115:
Dumped recording, 155.8 MB written to: /home/6_10_dump1.jfr
What version of the JDK are you using? The chunk should not need to be filled up.
There is a bug [1] that happens in JDK 11 or later, if you specify the filename of the file you want to dump at startup, but don't specify it when you dump the file.
Try this as a work around:
$ jcmd 115 JFR.dump filename=recording.jfr
[1] https://bugs.openjdk.java.net/browse/JDK-8220657
Azul support helped figure this out. If you don't specify the filename when starting the VM, then the following works:
XX:StartFlightRecording=disk=true,name=continuous_recording,dumponexit=true,maxsize=1024m,maxage=1d
This bug was filed and fixed as JDK-8220657. Azul said they will backport this to Zulu 8 and 11 in the future.
I have just installed Strawberry Perl 5.26 on a Win32 machine (XP), and installed Device::ParallelPort (with cpanm, and the installation is OK).
When I try to use the module, I have :
Device::ParallelPort unabel to create driver auto (see Device::ParallelPort::drv::auto for further information) - Device::ParallelPort::
drv::auto (auto detect) error
failed to load win32 - Can't locate Device/ParallelPort/drv/win32.pm in #INC (you may need to install the Device::ParallelPort::drv::win
32 module) (#INC contains: Q:/APPS/Perl-5.26/perl/site/lib/MSWin32-x86-multi-thread-64int Q:/APPS/Perl-5.26/perl/site/lib Q:/APPS/Perl-5
.26/perl/vendor/lib Q:/APPS/Perl-5.26/perl/lib) at (eval 3) line 2.
BEGIN failed--compilation aborted at (eval 3) line 2.
. Make sure you have loaded and installed Device::ParallelPort::drv::win32 from CPAN. Install Device::ParallelPort::drv::(linux|parport|
win32) and try again at (eval 2) line 3.
at Q:\VirtualDiskII\Perl\testlpt.pl line 25.
So I have installed Device::ParallelPort::drv::win32 (and the installation is OK). When trying to use the module, I have :
Device::ParallelPort unabel to create driver auto (see Device::ParallelPort::drv::auto for further information) - Device::ParallelPort::
drv::auto (auto detect) error
failed to load win32 - Failed to load inpout32.dll - Can't create Inp32 2 - Une requÛte d'envoi ou de rÚception de donnÚes n'a pas ÚtÚ a
utorisÚe car le socket n'est pas connectÚ et (lors de l'envoi sur un socket datagramme en utilisant un appel sendto) aucune adresse n'a
ÚtÚ fournie. at Q:/APPS/Perl-5.26/perl/site/lib/Device/ParallelPort/drv/win32.pm line 75.
. Make sure you have loaded and installed Device::ParallelPort::drv::win32 from CPAN. Install Device::ParallelPort::drv::(linux|parport|
win32) and try again at (eval 2) line 3.
at Q:\VirtualDiskII\Perl\testlpt.pl line 25.
Any ideas ?
Thank you by advance !
According to the Device::ParallelPort::drv::win32 docs...
Standard installation, but you also need "inpout32.dll" which may require either putting into your windows System directory, or at the location of your executable.
inpout32.dll actually comes from a 3rd party source and is freely available.
http://www.logix4u.net/inpout32.htm
Unfortunately that site appears to no longer work. You'll have to find another source.
If you wanted to get ambitious, you could patch the module to handle this automatically and, if the DLL's license allows, ship with the DLL. Or write an Alien wrapper module.
I am trying to setup VBS to talk HLA to a legacy app using LVCGame.
I am using openRTI currently in my project. I have LVCGame pointed to a directory with the following dlls:
RTI-NG.dll
OpenRIT.dll (copied from another folder)
libRTI-NG.dll (copy of RTI-NG.dll and renamed)
FedTime.dll
My vbsClient.config relevant lines:
Plugins = HLA-1.3.dll : HLA-1.3\Project\HLA.config
I am getting the following error out of LVCGame:
2014-12-31 10:48:03 INFO (LVCGAME::LVCGame::init) Initialised.
2014-12-31 10:48:03 ERROR (LVCGAME::LVCGame::start) 'class LVCGAME::UTILS::Exception' (src\LVCGame.cpp, line 766): Couldn't load plugin .\lib\HLA-1.3.dll. Error Code: 127
I did send an email to VBS support but it I had any idea what a 127 error was maybe I could get further.
I found that another free RTI Portico implementation is mentioned as working with LVCgame giving that a try has pretty similar results I get and error 126 instead of a 127.
2015-01-02 09:47:47 INFO (LVCGAME::UTILS::IOUtils::extractDllLoadPath) Using DLL path specified as 'D:\Program Files (x86)\Portico\portico-2.0.1\bin\vc10'.
2015-01-02 09:47:47 INFO (LVCGAME::LVCGame::init) Initialised.
2015-01-02 09:47:47 ERROR (LVCGAME::LVCGame::start) 'class LVCGAME::UTILS::Exception' (src\LVCGame.cpp, line 766): Couldn't load plugin .\lib\HLA-1.3.dll. Error Code: 126
2015-01-02 09:47:47 ERROR (LVCGAME::LVCGame::start) LVCGame start failed!
So eventually I found that Portico was creating a log file located in my VBS directory\logs. From there I was able to see that Portico at least was not able to find my .fed file I had the path messed up.
Just bought a new server that runs WHM/cPanel, same as the old. Trying to use the built in tool to migrate multiple accounts / packages over. I'm able to connect to the other server, it lists out all the packages & accounts, I select all and start the process.
Then it goes through each package and account and fails to copy anything over. This is the error given for a sample account:
Command failed with exit status 255
...etc...
Copying Suspension Info (if needed)...Done
Copying SSL certificates, CSRs, and keys...Privilege de-escalation before loading datastore either failed or was omitted. at /usr/local/cpanel/Cpanel/SSLStorage.pm line 1159
Cpanel::SSLStorage::_load_datastore('Cpanel::SSLStorage::Installed=HASH(0x3c72300)', 'lock', 1) called at /usr/local/cpanel/Cpanel/SSLStorage.pm line 1244
Cpanel::SSLStorage::_load_datastore_rw('Cpanel::SSLStorage::Installed=HASH(0x3c72300)') called at /usr/local/cpanel/Cpanel/SSLStorage/Installed.pm line 634
Cpanel::SSLStorage::Installed::_rebuild_records('Cpanel::SSLStorage::Installed=HASH(0x3c7230 0)') called at /usr/local/cpanel/Cpanel/SSLStorage.pm line 308
Cpanel::SSLStorage::__ANON__() called at /usr/local/cpanel/Cpanel/SSLStorage.pm line 1330
Cpanel::SSLStorage::_execute_coderef('Cpanel::SSLStorage::Installed=HASH(0x3c72300)', 'CODE(0x49ee958)') called at /usr/local/cpanel/Cpanel/SSLStorage.pm line 310
Cpanel::SSLStorage::rebuild_records('Cpanel::SSLStorage::Installed=HASH(0x3c72300)') called at /usr/local/cpanel/scripts/pkgacct line 2888
Script::Pkgacct::__ANON__('Cpanel::SSLStorage::Installed=HASH(0x3c72300)') called at /usr/local/cpanel/scripts/pkgacct line 2913
Script::Pkgacct::backup_ssl_for_user('jshea89', '/home/webwizard/cpmove-jshea89') called at /usr/local/cpanel/scripts/pkgacct line 532
Script::Pkgacct::script('Script::Pkgacct', '--use_backups', '--skiphomedir', 'jshea89', '/home/webwizard', '--split', '--compressed', '--mysql', 5.5, ...) called at /usr/local/cpanel/scripts/pkgacct line 111
==sshcontroloutput==
sh-4.1# exit $RET
exit
sh-4.1$ exit $RET
exit
sshcommandfailed=255`
A bit of a hack, but I went to /usr/local/cpanel/Cpanel/SSLStorage.pm line 1244 and commented out the Carp.
Accounts from my old dead server are now archiving :)
After some researching, I was able to determine that this was caused by incorrect ownership on the /home/user/ssl directory and its subdirectories. Someone had set the owner and group to root:root, when infact it should have been user:user.
Hopefully this helps some of you solve the problem!
I'm having a strange error trying to run a Perl script with ActivePerl on Windows XP:
>perl -d quick_translate_missing.pl < translate_en.txt > new.txt
Loading DB routines from perl5db.pl version 1.33
Editor support available.
Enter h or `h h' for help, or `perldoc perldebug' for more help.
main::(quick_translate_missing.pl:9):
9: my $not_translated = '\'EN_([\w\s]+)\'';
El sistema no puede hallar la ruta especificada.
Unknown error
Compilation failed in require at C:/Perl/lib/Term/ReadLine/Perl.pm line 65.
at C:/Perl/lib/Term/ReadLine/Perl.pm line 65
Term::ReadLine::Perl::new('Term::ReadLine', 'perldb', 'GLOB(0x1968f34)',
'GLOB(0x1927e7c)') called at C:/Perl/lib/perl5db.pl line 6068
DB::setterm called at C:/Perl/lib/perl5db.pl line 2241
DB::DB called at quick_translate_missing.pl line 9
Attempt to reload Term/ReadLine/readline.pm aborted.
Compilation failed in require at C:/Perl/lib/Term/ReadLine/Perl.pm line 65.
END failed--call queue aborted at quick_translate_missing.pl line 65.
at quick_translate_missing.pl line 65
"El sistema no puede hallar la ruta especificada." means "System cannot find the specified path". The line the error is referring to is from Perl.pm:
eval {require Term::ReadLine::readline}; die $# if $#;
What I understand is that it cannot find Term::ReadLine::readline, but the file C:\Perl\lib\Term\ReadLine\readline.pm is there. Also PATH is set correctly since I can run perl interpreter from anywhere without specifing the path.
The error happens only when using standard output redirection (>). Script passed to debugger doesn't matter, it crashes on all if output redirection used.
Any clues? Thanks in advance!
This may not help you if you must have a specific perl version, but I found this same error with my perl 5.8.5 install. I could not upgrade on one machine (for legacy code reasons), but I ran it in another perl environment with the latest perl (v5.14.2) and this "debugger" bug has been solved (although I suspect you may have the same result by updating the Term::ReadLine::* modules as well). By the way, this isn't specific to ActivePerl -- I saw this on Linux as well.