Linux Deployment Zen Path and default port modifications and attachment size restrictions modification and use of various pits

Linux Deployment Zen Path and default port modifications and attachment size restrictions modification and use of various pits

• This blog will share my experience in the use of Zen Tao is a lot of problems I hope to be helpful to everyone
• Some of the problems just found out, but now the ability can't solve the hope that the big guy can give some advice to help

Reference documents:
http://www.zentao.net/

• The use of this Zen road will not give you more explanations, directly into the topic:
  The installation package required for the experiment:
  Link: https://pan.baidu.com/s/1UZaJeO5RFdlkPmSVlrdopw Password: uame

Note: Official online can also be directly downloaded, on the official Internet has four connections, the international version of everyone can feel free, personal sleep or local use, but in the site one and site 22 path download Zentao package installed in the initial usage and file upload is still a little different, site one in the upload with large attachments is, We do not see whether the click Success, but the site two can be seen intuitively, so the recommended download site two:

Here we directly install the latest version of Zen Road 10.0 version, this version only optimized the graphical interface, but also filled many previous versions of the bug

First we need to install Lrzsz:

yum -y install lrzsz

Get us ready. Import/USR/LOCAL/SRC into a subcontract

Unzip the file:

tar zxf /usr/local/src/ZenTaoPMS.10.0.stable.zbox_64.tar.gz.tgz -C /opt/

• Note: Here I installed the Linux one-click installation package is the official method is directly extracted to the/opt/directory directly to start the line, if the decompression to other directories may be directory permissions problems, directly to 777 permissions are not, so we still do not complete those of the moth, their own official instructions can be If there is a list of mandatory requirements can refer to the official website other installation methods

Unzip it in this directory and we can start the Zen road directly.

• Here are the basic operation commands for Zen Trails
  Start Zen Road:

  sh /opt/zbox/zbox start

  Close Zen Road:

  sh /opt/zbox/zbox stop

  Restart Zen Road:

  sh /opt/zbox/zbox restart

  To modify the default Apache port:

  sh /opt/zbox/zbox -ap [port]

  To modify the default MySQL port:

  sh /opt/zbox/zbox -mp [port]

Note: One-click installation package is to integrate both HTTP and MySQL into the Zentao installation (the default HTTP port is 80,mysql is 3306, Ken can have port conflicts so we recommend modifying the default port), so we do not need to install additional, if you do not want to use the MySQL database, You can choose a different installation method
First we modify Apache port and MySQL Port:

sh /opt/zbox/zbox -ap 9090sh /opt/zbox/zbox -mp 3307

Start Zentao:

sh /opt/zbox/zbox start

As follows:

Show success said we succeeded, but we had to catch the port monitor:

This means that we have succeeded, and we can view it by visiting the Web:

If you modified the access to Apache ports:

http://ip:[Apache port]

If you do not modify the direct access IP (web default is 80):

http://ip

The visit was successful as follows: (click on the open source version and we can start the Zen journey.)

After entering we can set the locale:

Of course, the default Chinese is good, this time someone will have questions, how to login user and password, I have not created Ah, is not I wrong ah, accidentally created, or omitted which step ah, since you see this document then I tell you, this is not called a thing, After the Zen Road 10.0 version in order to enhance security, in the first sign-in we need the initial password, of course, can also be seen on the internet, but a lot of nonsense, the correct user name and polygon are:

user：adminpassword：123456

After login the system will let us change the password

The original password is our initial password: 123456

At this point we are ready to install the deployment to this end can be used, the following is to say is the pit and some extensibility things

Start Zen Lane times wrong:
First we need to check MySQL and Apache log information for any errors

If there is an error, according to the error to troubleshoot, but general startup failure has a few questions:

• Insufficient user rights to start, either using root or sudo (personal advice)
• See if Apache and MySQL ports are occupied
• The TAR package decompression location is problematic, not placed in the/OPT directory

There is a lot of error information in Errror_log after the Zen road starts.
Such as:

[Tue 02 10:07:44.338117 2017] [Mpm_event:alert] [PID 746:tid 2913958720] (11) Resource temporarily unavailable:apr_thread_create:unable to create worker Thread[tue 10:07:44.342509] [mpm_ Event:crit] [pid 746:tid 2901408576] (a) Invalid argument:ap_queue_pop failed[tue-10:07:44.342585] [mpm_event : Crit] [pid 746:tid 2901408576] (argument:ap_queue_pop) Invalid failed[tue 10:07:44.342590 ] [PID 746:tid 2901408576] (Invalid argument:ap_queue_pop failed[tue) 10:07:44.342593] [Mpm_event:crit] [pi D 746:tid 2901408576] (Invalid argument:ap_queue_pop failed[tue) [10:07:44.342598] [PID 746 : Tid 2901408576] (Invalid argument:ap_queue_pop failed[tue 10:07:44.342604] [Mpm_event:crit] [PID 746:tid 2901408576] (Invalid argument:ap_queue_pop failed[tue 10:07:44.342609] [Mpm_event:crit] [PID 746:tid 29014 08576] (Invalid argument:ap_queue_pop failed[tue 02 10:07: 44.342613] [Mpm_event:crit] [pid 746:tid 2901408576] ($) Invalid argument:ap_queue_pop failed[tue 02 10:07:44.3  42616] [Mpm_event:crit] [pid 746:tid 2901408576] ($) Invalid argument:ap_queue_pop failed[tue 02 10:07:44.342620 [Mpm_event:crit] [PID 746:tid 2901408576] (22) Invalid argument:ap_queue_pop failed[tue 10:07:44.342623] [Mpm_event:crit] [pid 746:tid 2901408576] (Inval) ID Argument:ap_queue_pop failed

To solve the direction of thinking:

• In general, this is a protection script or resource limit for server deployment, and the server rejects the application of Zen Road to resources

The problem of Zen Road database

• The local MySQL database was hung after Zen Road started.
• Database start error when Zen Road starts
• After the Zen path starts, MySQL has port monitoring but no process ID (this is typically common in docker containers)

To solve the direction of thinking:

• The local database starts with Port 3306, Zen Lane One-click installation package starts with 3306 ports, so port conflicts occur when booting

• There is also an error in executing sh/opt/zbox/zbox restart display:
  
  Let's do it first:

  sh /opt/zbox/zbox stop在执行：sh /opt/zbox/zbox start

• Zen Road start when the database times wrong, if there is no port conflict in the case of also reported wrong, then probably the MySQL library directory permissions are not correct, need to ensure that MySQL permissions are as follows:
  

• The deployment of Zen Road in Docker, start and log are not error, but in the catch port monitoring found that Apache is not abnormal, but MySQL only port monitoring and no port to listen to the corresponding process ID, such as:
  
  This figure can be seen that Apache is normal, but MySQL extreme exception, but do not affect the normal use of Zen, this problem I found a special number of information did not find the cause and solution, if someone encountered the same problem want to discuss with each other

Modify Zen Path default attachment upload size
Default in Zen Channel attachment upload size is 50M, more than 50M can not upload

Workaround:
Modify the php.ini file

vim /opt/zbox/etc/php/php.ini

Where to modify:

To modify a configuration file:

cd /opt/zbox/app/zentao/www/

Modify two configuration files, these two profiles are shadow, view way:

ll -a /opt/zbox/app/zentao/www/

As follows:

The two configuration files need to be modified in each place:
. htaccess

. ztaccess

To restart Zen Road:

sh /opt/zbox/zbox restart

To see if the modification was successful:

At this point the attachment has been shown to upload 500M

Zen path attachment has changed size but still uploading failed show network timeout or network error
As follows:

Problem-Solving ideas:
Before we solve the problem, we need to understand the Ajax, the problem is due to the speed of the AJAX default 30 timeout caused by failure
Ajax:

Ajax使用 JavaScript 向服务器提出请求并处理响应而不阻塞用户！核心对象XMLHTTPRequest。通过这个对象，您的 JavaScript 可在不重载页面的情况与 Web 服务器交换数据，即在不需要刷新页面的情况下，就可以产生局部刷新的效果。Ajax 在浏览器与 Web 服务器之间使用异步数据传输（HTTP 请求），这样就可使网页从服务器请求少量的信息

The default Ajax time response time is 30S, when we upload the file size divided by no second upload bandwidth more than 30 when the error will be incorrect connection timeout, network connection failure this type of errors
We need to change the default response time for Ajax

Use Nginx to resolve domain name Login Zen Road upload attachment problem, but use IP and port login upload but no problem

When we upload one or two MB of attachments, the page will show a network error, or timeout

Solution Ideas:
When this happens, the log in our program does not have an error message, so we can only view the browser's actions via the browser (we suggest using Google, right-click to view or press F12) such as:

In this case we can see that the page return information is Nginx, and the information is too large
At this point we should understand the problem is that, nginx upload file size By default is 1M, so I just modify the configuration can be:
Edit the Nginx Master file and add a line of configuration in the http{} field:

client_max_body_size 100m;

• Change the upload size to 100M, but the actual situation depends on the speed, because the Ajax default time is 30S
  Re-load the Nginx after modification:

  nginx -s reload

• OK, the whole blog to this end, hope to read this blog after the Zen Road can be a little detour, if you encounter problems, or the document has the wrong place welcome to discuss the exchange, contact information:
  qq:1715721936

Linux Deployment Zen Path and default port modifications and attachment size restrictions modification and use of various pits