I am trying to install joomla 2.5 but in step-4, which is database, there is a some problem occur so that I can not install it.
what is problem?
I am using wamp.
Please install new version of Wamp because I have use wamp and I install joomla 2.5 and joomla 3.0 easily in my wamp server2.4.
Please Follow this step in step 4:
1) Select Databse type : mysql
2) Hostname : localhost
3) username : root
4) Password: (blank)
5) Databse name: xyz
6) Old databse process : backup
Related
I am new to moodle and trying to install moodle 3.3.1 on my windows system, but after some steps it is showing some errors.
mysql_full_unicode_support#File_format: Your database has tables using Antelope as the file format. Full UTF-8 support in MySQL and MariaDB requires the Barracuda file format. Please convert the tables to the Barracuda file format.
mysql_full_unicode_support#Large_prefix: For full support of UTF-8 both MySQL and MariaDB require you to change your MySQL setting 'innodb_large_prefix' to 'ON'. See the documentation for further details.
site not https: It has been detected that your site is not secured using HTTPS. It is strongly recommended to migrate your site to HTTPS for increased security and improved integration with other systems.
please help me to resolve these errors. i am trying to install moodle on my windows system using xampp server. (localhost)
You seem to be having 3 problems
1. Your DB tables are in an earlier format and needs to be upgraded to Barracuda
Moodle created an easy fix for the first problem, before going ahead with the upgrade, you can run the following script from your server, it will upgrade the problematic tables to the Barracuda format
The following command will give you the list of tables that needs to be updated
$ php /path/to/moodle/admin/cli/mysql_compressed_rows.php --list
Then run the fix
$ php /path/to/moodle/admin/cli/mysql_compressed_rows.php --fix
The following link will give you the steps and guide you through the update, the above scripts are from that link
https://docs.moodle.org/28/en/Administration_via_command_line#Converting_InnoDB_tables_to_Barracuda
2. You are having Unicode problems
As of Moodle 3.2, utf8mb4 is used, some changes are required, these answers have been provided before but here they are just in case.
You will first need to edit your my.cnf file and add the following:
[client]
default-character-set = utf8mb4
[mysqld]
innodb_file_format = Barracuda
innodb_file_per_table = 1
innodb_large_prefix
character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci
skip-character-set-client-handshake
[mysql]
default-character-set = utf8mb4
Restart your MySQL service and run the following script:
$ php /path/to/moodle/admin/cli/mysql_collation.php --collation=utf8mb4_unicode_ci
Then modify your config.php file:
$CFG->dboptions = array(
…
'dbcollation' => 'utf8mb4_unicode_ci',
…
);
The documentation can be found at the following location:
https://docs.moodle.org/32/en/MySQL_full_unicode_support
3. Your site is not SSL
To make your site SSL you will need to get a SSL certificate from a trusted store such as entrust.
First search result in Google for the error message + "Moodle":
https://docs.moodle.org/33/en/MySQL_full_unicode_support
This answer assumes that you are trying to fix the error on a local installation using xampp.
This is what I did:
first
if you are using xampp on windows, then on your xampp control panel, locate the MYSQL config button and click to see the my.ini option, this is what is called my.cnf on other platforms.
Second
Copy the following text into the my.ini file.
[client]
default-character-set = utf8mb4
[mysqld]
innodb_file_format = Barracuda
innodb_file_per_table = 1
innodb_large_prefix
character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci
skip-character-set-client-handshake
[mysql]
default-character-set = utf8mb4
Third
restart the MYSQL and the error is gone!
How can I setup Oracle Apex (application express) to send emails through my Gmail account without using my own SMTP ?
Background :
Apex 5.0.3 is installed with Oracle XE 11.2 installed on Centos
(linux) 6.x
SMTP is not required to be enabled on centos. We will use gmail one
directly.
Solution is based on windows implementation published by : HÅVARD KRISTIANSEN at
:
http://monkeyonoracle.blogspot.com/2009/11/plsql-and-gmail-or-utlsmtp-with-ssl.html
Will use stunnel to communicate with gmail directly.
Apex / Oracle XE installation instructions are not included.
Installation (written out of my head) :
1.Install stunnel as root :
yum install stunnel -y
2.create a conf file for stunnel using nano or vi (to install nano : yum install nano -y )
nano /etc/stunnel/stunnel.conf
3.Enter the following to new stunnel.conf created:
; Use it for client mode
client = yes
[ssmtp]
accept = 1925
connect = smtp.gmail.com:465
4.restart stunnel using whatever method, e.g kill -9 and start using the following command :
/usr/bin/stunnel
5.Log in to apex as admin : http://yourhost:port/ords/apex_admin
Go to : Manage instance -> instance settings.
6.Put the following settings :
SMTP Host Address : 127.0.0.1 (or your local)
SMTP Host Port : 1925 (as u can see in stunnel.conf above).
SMTP Authentication Username : your gmail username : etai.guday (WITHOUT #gmail.com)
SMTP Authentication Password : gmail password
Use SSL/TLS : NO
Default Email From Address : etai.guday#gmail.com (including #gmail.com)
7.Due to gmail restrictions YOU MUST enable : https://g.co/allowaccess to use the above method (with relevant gmail account).
8.Enable Oracle DB ACL by using example bellow
https://www.dropbox.com/s/2ieaawy5gme9a50/email_configuration_acl_for_apex.txt?dl=0
All above should work :-) didn't have time to test it further or refer to security issues etc
I have a EC2 instance running CentOS and PBX on a flash installed.
I can connect to server using SSH. I want to reset PBX passwords, so i run:
passwd-master
after following steps, i get an error at the end :
Your manual password was accepted!
passwd-master - 2.0.4 released on 082612
CentOS release 6.3 (Final) - 64 Bit
**********************************************************************
* Now applying new password to maint/meetme/wwwadmin *
**********************************************************************
Applying wwwadmin password
Applying maint password
Applying meetme password
httpd service restarted to apply new passwords!
passwd-master - 2.0.4 released on 082612
CentOS release 6.3 (Final) - 64 Bit - ARI PATCH
**********************************************************************
* Now patching main.conf.php *
**********************************************************************
Now verifying /var/www/html/recordings/includes/main.conf.php exists
ERROR the file /var/www/html/recordings/includes/main.conf.php DOES NOT EXIST
or is zero length. Unable to continue now exiting
I noticed i dont have permission to access this folder : "/var/www/html/recordings/includes/"
Then i tried to set password of "maint" only, and i got an error at the end again :
passwd-maint
-------------------------------------------
Set password for AMP web GUI and maint GUI
User: maint
-------------------------------------------
New password:
Re-type new password:
Updating password for user maint
htpasswd: unable to update file /usr/local/apache/passwd/wwwpasswd
And its because i dont have access to "wwwpasswd" (not even read permission)
I login using default EC2-user obviously.
My question is, how can i fix this problem and change passwords?
I tried to use : sudo su command
and then run passwd-master , but it doesnt work.
after i use sudo su command, it doesnt know passwd-master and passwd-maint anymore and i get
bash: passwd-master: command not found
error.
Any advise please?
If its not in the path, then you have to run it like this ./passwd-master while in the directory where the script exists. – datasage
Thank you datasage. using " ./ " solved my problem . i didn't know about it.
I am trying to setup a basic ldap server/client scenario. I downloaded openldap for windows and installed it. I am starting the server successfully with the command,
slapd -d 1
I tried to use various clients (commandline, LDAP Browser, phpLDAPadmin) to connect and do a search, it works with 'anonymous access' but it fails every time I try the same with root user/password and says 'failed to connect to ldap://localhost:389'. Same thing works if i connect anonymously.
What could be the problem ?
Here's my slapd.conf
ucdata-path ./ucdata
include ./schema/core.schema
pidfile ./run/slapd.pid
argsfile ./run/slapd.args
database bdb
suffix "dc=guessant,dc=org"
rootdn "cn=Manager,dc=guessant,dc=org"
rootpw secret
directory ./data
I am using Login DN as "cn=Manager,dc=guessant,dc=org" and password as "secret"
It has been fixed now .. problem was with PHP mcrypt and phpLdapAdmin. Apparantly there's an issue with PHP 5.2. and figured out that upgrading to 5.3 + or removing mcrypt usage, would fix it. I chose the later, for the timebeing atleast
I got Postgres 8.4 installed on my mac with Snow Leopard. I know the 'postgres' user was created but I have no idea what the default password is. How should I login to the database?
http://archives.postgresql.org/pgsql-admin/2001-10/msg00192.php and similar internet resources may answer your question. Supposedly, there is no password by default.
For future readers...
I had a similar problem. After installing Postgres 9.1, the password I supplied to the installer didn't allow me to connect to the database using pgadmin 3. This is what I had to do to fix it:
Configure so you can log in without a password:
Stop the postgres server (launch daemon):
sudo launchctl unload /Library/LaunchDaemons/com.edb.launchd.postgresql-9.1.plist
Edit data/pg_hba.conf and change 'md5' to 'trust' in the 'local'
'127.0.0.1/32' line.
Start the daemon
sudo launchctl load /Library/LaunchDaemons/com.edb.launchd.postgresql-9.1.plist
Connect using pgadmin 3 and re-set the password
Start pgadmin 3 and connect to the database (right click 'Connect' on the Postgres 9.1 server).
Under Login roles, right-click the 'posgres' user, select 'Properties...' and reset the password on the 'Definition' tab panel.
Then disconnect pgadmin 3 from the database (right-click 'Disconnect' on the Postgres 9.1 server).
Configure the server so it requires a password again:
Stop the daemon (as per step 1.1).
Edit data/pg_hba.conf and change 'trust' back to 'md5' in the
'local' '127.0.0.1/32' line.
Start the daemon (as per step 1.3).