Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
31
Information / Re: Yellow icons in the SERVICES STATUS, why?
« on: November 25, 2016, 03:53:56 PM »
But seriously yellow is not being English? 
Yellow looks like a warning. The developers of CWP not should use yellow icons for that.
Thanks for your replies.
Yellow looks like a warning. The developers of CWP not should use yellow icons for that.
Thanks for your replies.
32
Information / Re: Yellow icons in the SERVICES STATUS, why?
« on: November 17, 2016, 04:00:09 AM »
Really???
And how can I change it?
And how can I change it?
33
Information / Yellow icons in the SERVICES STATUS, why?
« on: November 16, 2016, 02:05:24 AM »
I have this in my panel
Why?
What does it mean?
Why are they not green?
Thanks
Why?
What does it mean?
Why are they not green?
Thanks
34
Updates / Re: BUG when you upgrade the VPS
« on: September 01, 2016, 07:26:45 AM »
I have found the solution:
It is very simple:
It can be useful for you.
It is very simple:
Code: [Select]
resize2fs /dev/vda1It can be useful for you.
35
Updates / Re: BUG when you upgrade the VPS
« on: September 01, 2016, 06:27:03 AM »
I have not hosting support. It is my server.
I want to learn, I don't want to go to the support.
So... Is impossible to resize a partition where the CWP is running actually
How can I do it ?
I want to learn, I don't want to go to the support.
So... Is impossible to resize a partition where the CWP is running actually
How can I do it ?
36
Updates / Re: BUG when you upgrade the VPS
« on: August 30, 2016, 05:50:49 AM »
Ok, I think you are right.
Sorry for my doubts.
But when I try to resize the partition, I have the error 16.
So.. can I solve it if the CWP is in use ?
When I reboot the VPS, nothing is change.
Where is my problem?
This was my way:
Sorry for my doubts.
But when I try to resize the partition, I have the error 16.
So.. can I solve it if the CWP is in use ?
When I reboot the VPS, nothing is change.
Where is my problem?
This was my way:
Code: [Select]
[root@vps****01 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 9,8G 5,5G 3,8G 59% /
tmpfs 1,9G 0 1,9G 0% /dev/shm
[root@vps****01 ~]# fdisk -ul /dev/vda
Disk /dev/vda: 21.5 GB, 21474836480 bytes
16 heads, 63 sectors/track, 41610 cylinders, total 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000574cf
Device Boot Start End Blocks Id System
/dev/vda1 * 2048 41943039 20970496 83 Linux
[root@vps****01 ~]# fdisk -u /dev/vda
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c').
Command (m for help): d
Selected partition 1
Command (m for help): 1
1: unknown command
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help): p
Disk /dev/vda: 21.5 GB, 21474836480 bytes
16 heads, 63 sectors/track, 41610 cylinders, total 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000574cf
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First sector (63-41943039, default 63): 2048
Last sector, +sectors or +size{K,M,G} (2048-41943039, default 41943039): 41943039
Command (m for help): p
Disk /dev/vda: 21.5 GB, 21474836480 bytes
16 heads, 63 sectors/track, 41610 cylinders, total 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000574cf
Device Boot Start End Blocks Id System
/dev/vda1 2048 41943039 20970496 83 Linux
Command (m for help): a
Partition number (1-4): 1
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
WARNING: Re-reading the partition table failed with error 16: Dispositivo o recurso ocupado.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.
37
Updates / Re: BUG when you upgrade the VPS
« on: August 24, 2016, 06:06:44 PM »
Hi
I think my new partition is 20gb, the CWP is wrong when it show only 10gb.
It is wrong when it shows that 4'7gb are used.
I had 9'99 gb of my 10 GB used... upgrade to 20 GB of space and now I have ONLY 4'7 in use ?? It is impossible.
CWP is wrong.
I think my new partition is 20gb, the CWP is wrong when it show only 10gb.
It is wrong when it shows that 4'7gb are used.
I had 9'99 gb of my 10 GB used... upgrade to 20 GB of space and now I have ONLY 4'7 in use ?? It is impossible.
CWP is wrong.
38
Updates / BUG when you upgrade the VPS
« on: August 23, 2016, 05:09:56 AM »
Hi
I have working a CWP in my VPS.
Today, I have upgraded my VPS and the CWP continue working, but the DISK DETAILS of the partition is wrong.
My virtual DISC ( 10 gb ) was full, 99%. Now I have 20gb and this is the info of the partition in CWP:
Now, the 50% I think is ok, but the size isn't.
I have working a CWP in my VPS.
Today, I have upgraded my VPS and the CWP continue working, but the DISK DETAILS of the partition is wrong.
My virtual DISC ( 10 gb ) was full, 99%. Now I have 20gb and this is the info of the partition in CWP:
Code: [Select]
Fdisk info:
Disk /dev/vda: 21.5 GB, 21474836480 bytes
16 heads, 63 sectors/track, 41610 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000574cf
Device Boot Start End Blocks Id System
/dev/vda1 * 3 20806 10484736 83 Linux
Software RAID:
Personalities :
unused devices:
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 9.8G 4.7G 4.7G 50% /
tmpfs 1.9G 0 1.9G 0% /dev/shmNow, the 50% I think is ok, but the size isn't.
39
MySQL / Re: Reinstalled CWP and now mysql doesn't work
« on: August 14, 2016, 11:12:56 PM »
RESOLVED !!
The problem was the permission of the folders.
I have fixed it with this: http://forum.centos-webpanel.com/php/suphp-500-internal-server-error/
Regards.
The problem was the permission of the folders.
I have fixed it with this: http://forum.centos-webpanel.com/php/suphp-500-internal-server-error/
Regards.
40
Installation / Re: CWP down, I am scared
« on: August 14, 2016, 11:12:03 PM »RESOLVED !!!
The problem is when you upload with ROOT permission.
cwp doesn't work nice.
The solution is here:
http://forum.centos-webpanel.com/php/suphp-500-internal-server-error/
Thanks
41
MySQL / Reinstalled CWP and now mysql doesn't work
« on: August 13, 2016, 11:25:05 PM »
I have reinstalled the CWP, copy the files, created the database, and import the another database to the new datebases, but now they don't work.
Why?
I have this log:
Why?
I have this log:
Code: [Select]
160813 01:19:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160813 1:19:09 InnoDB: Initializing buffer pool, size = 8.0M
160813 1:19:09 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
160813 1:19:09 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
160813 1:19:09 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
160813 1:19:09 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
160813 1:19:09 InnoDB: Started; log sequence number 0 0
160813 1:19:09 [Note] Event Scheduler: Loaded 0 events
160813 1:19:09 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
160813 1:19:10 [Note] /usr/libexec/mysqld: Normal shutdown
160813 1:19:10 [Note] Event Scheduler: Purging the queue. 0 events
160813 1:19:10 InnoDB: Starting shutdown...
160813 1:19:15 InnoDB: Shutdown completed; log sequence number 0 44233
160813 1:19:15 [Note] /usr/libexec/mysqld: Shutdown complete
160813 01:19:15 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160813 01:19:15 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160813 1:19:15 InnoDB: Initializing buffer pool, size = 8.0M
160813 1:19:15 InnoDB: Completed initialization of buffer pool
160813 1:19:15 InnoDB: Started; log sequence number 0 44233
160813 1:19:16 [Note] Event Scheduler: Loaded 0 events
160813 1:19:16 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
160813 1:42:11 [Note] /usr/libexec/mysqld: Normal shutdown
160813 1:42:11 [Note] Event Scheduler: Purging the queue. 0 events
160813 1:42:11 InnoDB: Starting shutdown...
160813 1:42:13 InnoDB: Shutdown completed; log sequence number 0 103628
160813 1:42:13 [Note] /usr/libexec/mysqld: Shutdown complete
160813 01:42:13 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160813 01:42:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160813 1:42:30 InnoDB: Initializing buffer pool, size = 8.0M
160813 1:42:30 InnoDB: Completed initialization of buffer pool
160813 1:42:30 InnoDB: Started; log sequence number 0 103628
160813 1:42:30 [Note] Event Scheduler: Loaded 0 events
160813 1:42:30 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
160813 7:33:09 [Note] /usr/libexec/mysqld: Normal shutdown
160813 7:33:09 [Note] Event Scheduler: Purging the queue. 0 events
160813 7:33:09 InnoDB: Starting shutdown...
160813 7:33:12 InnoDB: Shutdown completed; log sequence number 0 72426297
160813 7:33:12 [Note] /usr/libexec/mysqld: Shutdown complete
160813 07:33:12 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160813 07:33:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160813 7:33:12 InnoDB: Initializing buffer pool, size = 64.0M
160813 7:33:12 InnoDB: Completed initialization of buffer pool
160813 7:33:12 InnoDB: Started; log sequence number 0 72426297
160813 7:33:12 [Note] Event Scheduler: Loaded 0 events
160813 7:33:12 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
160813 7:36:32 [Note] /usr/libexec/mysqld: Normal shutdown
160813 7:36:32 [Note] Event Scheduler: Purging the queue. 0 events
160813 7:36:32 InnoDB: Starting shutdown...
160813 7:36:34 InnoDB: Shutdown completed; log sequence number 0 72426297
160813 7:36:34 [Note] /usr/libexec/mysqld: Shutdown complete
160813 07:36:34 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160813 07:37:10 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160813 7:37:10 InnoDB: Initializing buffer pool, size = 64.0M
160813 7:37:10 InnoDB: Completed initialization of buffer pool
160813 7:37:10 InnoDB: Started; log sequence number 0 72426297
160813 7:37:10 [Note] Event Scheduler: Loaded 0 events
160813 7:37:10 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
42
Installation / Re: CWP down, I am scared
« on: August 13, 2016, 11:23:01 PM »
Thanks, I used it and reinstall the CWP.
But now, the date bases don't work, do you now the reason??'
In the log I have it:
But now, the date bases don't work, do you now the reason??'
In the log I have it:
Code: [Select]
160813 01:19:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160813 1:19:09 InnoDB: Initializing buffer pool, size = 8.0M
160813 1:19:09 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
160813 1:19:09 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
160813 1:19:09 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
160813 1:19:09 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
160813 1:19:09 InnoDB: Started; log sequence number 0 0
160813 1:19:09 [Note] Event Scheduler: Loaded 0 events
160813 1:19:09 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
160813 1:19:10 [Note] /usr/libexec/mysqld: Normal shutdown
160813 1:19:10 [Note] Event Scheduler: Purging the queue. 0 events
160813 1:19:10 InnoDB: Starting shutdown...
160813 1:19:15 InnoDB: Shutdown completed; log sequence number 0 44233
160813 1:19:15 [Note] /usr/libexec/mysqld: Shutdown complete
160813 01:19:15 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160813 01:19:15 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160813 1:19:15 InnoDB: Initializing buffer pool, size = 8.0M
160813 1:19:15 InnoDB: Completed initialization of buffer pool
160813 1:19:15 InnoDB: Started; log sequence number 0 44233
160813 1:19:16 [Note] Event Scheduler: Loaded 0 events
160813 1:19:16 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
160813 1:42:11 [Note] /usr/libexec/mysqld: Normal shutdown
160813 1:42:11 [Note] Event Scheduler: Purging the queue. 0 events
160813 1:42:11 InnoDB: Starting shutdown...
160813 1:42:13 InnoDB: Shutdown completed; log sequence number 0 103628
160813 1:42:13 [Note] /usr/libexec/mysqld: Shutdown complete
160813 01:42:13 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160813 01:42:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160813 1:42:30 InnoDB: Initializing buffer pool, size = 8.0M
160813 1:42:30 InnoDB: Completed initialization of buffer pool
160813 1:42:30 InnoDB: Started; log sequence number 0 103628
160813 1:42:30 [Note] Event Scheduler: Loaded 0 events
160813 1:42:30 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
160813 7:33:09 [Note] /usr/libexec/mysqld: Normal shutdown
160813 7:33:09 [Note] Event Scheduler: Purging the queue. 0 events
160813 7:33:09 InnoDB: Starting shutdown...
160813 7:33:12 InnoDB: Shutdown completed; log sequence number 0 72426297
160813 7:33:12 [Note] /usr/libexec/mysqld: Shutdown complete
160813 07:33:12 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160813 07:33:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160813 7:33:12 InnoDB: Initializing buffer pool, size = 64.0M
160813 7:33:12 InnoDB: Completed initialization of buffer pool
160813 7:33:12 InnoDB: Started; log sequence number 0 72426297
160813 7:33:12 [Note] Event Scheduler: Loaded 0 events
160813 7:33:12 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
160813 7:36:32 [Note] /usr/libexec/mysqld: Normal shutdown
160813 7:36:32 [Note] Event Scheduler: Purging the queue. 0 events
160813 7:36:32 InnoDB: Starting shutdown...
160813 7:36:34 InnoDB: Shutdown completed; log sequence number 0 72426297
160813 7:36:34 [Note] /usr/libexec/mysqld: Shutdown complete
160813 07:36:34 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160813 07:37:10 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160813 7:37:10 InnoDB: Initializing buffer pool, size = 64.0M
160813 7:37:10 InnoDB: Completed initialization of buffer pool
160813 7:37:10 InnoDB: Started; log sequence number 0 72426297
160813 7:37:10 [Note] Event Scheduler: Loaded 0 events
160813 7:37:10 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
43
Installation / Re: CWP down, I am scared
« on: August 11, 2016, 06:58:17 AM »
What is wrong if now the server is fully down?
The websites don't load.
I can't do ping to any domain.. and I can't do ping to the IP of the VPS.
I can't loggin in CWP.
What file can do that?
(I only have access to the VPS in rescue mode, via SSH)
The websites don't load.
I can't do ping to any domain.. and I can't do ping to the IP of the VPS.
I can't loggin in CWP.
What file can do that?
(I only have access to the VPS in rescue mode, via SSH)
44
Installation / CWP down, I am scared
« on: August 10, 2016, 09:35:54 PM »
Good afternoon.
I have a VPS on which I installed CWP. and everything has worked well for months.
Yesterday, I don't know the reason, but the VPS has stopped working.
I have the VPS at OVH, I put the VPS in recue mode, they have tested everything and they say that the problem is the configuration, that the VPS is well.
Do I only have SSH access, I can do now to avoid losing information? is possible to reinstall CWP without losing all the accounts? I have a lot of things there and I don't know how to find the BUG in my CWP.
I have a VPS on which I installed CWP. and everything has worked well for months.
Yesterday, I don't know the reason, but the VPS has stopped working.
I have the VPS at OVH, I put the VPS in recue mode, they have tested everything and they say that the problem is the configuration, that the VPS is well.
Do I only have SSH access, I can do now to avoid losing information? is possible to reinstall CWP without losing all the accounts? I have a lot of things there and I don't know how to find the BUG in my CWP.
45
E-Mail / How to read the ROOT MAILS ?
« on: August 09, 2016, 12:11:24 AM »
Hi,
my root mail is 2 Gb now, I can see it in /var/mail/root
But how can I log in?
Roundcube doesn't working for the user "root", it only works with emails accounts.
I want to explore these emails, delete them...
Regards.
my root mail is 2 Gb now, I can see it in /var/mail/root
But how can I log in?
Roundcube doesn't working for the user "root", it only works with emails accounts.
I want to explore these emails, delete them...
Regards.
