Closed noradwc closed 6 years ago
Insufficient information.
Hi Fedor,
Here`s the information you requested:
1- You didn't provide any information about your server environment.
~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 7.7 (wheezy) Release: 7.7 Codename: wheezy Apache 2.2.x and PHP 5.2.x
2- How often does this issue happen? Have you reproduced the issue yourself?
No, we were unable to reproduce the problem ourselves. This happens 2-3 times per week, Here a couple more examples: https://www.screencast.com/t/FFqC0JxxU https://www.screencast.com/t/iQ6XqQEhy
3- Are there any errors in your server logs?
No error log for mibew vhost.
4- Are there any errors in the developer's console in browser?
Sorry, I do not know how to access developers console.
Thank you,
Nora
On Mon, Jul 16, 2018 at 5:55 PM Fedor A. Fetisov notifications@github.com wrote:
Insufficient information.
- You didn't provided any information about your server environment.
- How often does this issue happens? Have you reproduced the issue yourself?
- Are there any errors in your server logs?
- Are there any errors in the developers console in browser?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Mibew/mibew/issues/230#issuecomment-405378918, or mute the thread https://github.com/notifications/unsubscribe-auth/AIyvEI6E7Mq7zAkoU1ldnEKzbBK3lbPqks5uHP2jgaJpZM4VRtsQ .
It's impossible to solve the issue that one is unable to reproduce.
Apache 2.2.x and PHP 5.2.x
Your PHP version is lower than required (i.e. 5.4+). It's not necessary the reason for the issue, but it could be.
No error log for mibew vhost.
Do you mean that there are no errors in the log, or that you're unable to access the log?
Sorry, I do not know how to access developers console.
https://developers.google.com/web/tools/chrome-devtools/console/
Hi Fedor,
You are correct, it`s impossible to solve something that cannot be replicated. We will start by trying to enhance the PHP version. Thank you!
Nora
On Wed, Jul 18, 2018 at 12:18 PM Fedor A. Fetisov notifications@github.com wrote:
1.
It's impossible to solve the issue that one is unable to reproduce. 2.
Apache 2.2.x and PHP 5.2.x
Your PHP version is lower than required https://mibew.org/features#requirements (i.e. 5.4+). It's not necessary the reason for the issue, but it could be.
1.
No error log for mibew vhost.
Do you mean that there are no errors in the log, or that you're unable to access the log?
1.
Sorry, I do not know how to access developers console.
https://developers.google.com/web/tools/chrome-devtools/console/
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Mibew/mibew/issues/230#issuecomment-405968843, or mute the thread https://github.com/notifications/unsubscribe-auth/AIyvENEHs63Z-HBoFFUTRzXeKEkg0C5Jks5uH1HNgaJpZM4VRtsQ .
Hi Fedor,
Latest update from our Sysadmins:
Sorry, My bad, I was giving wrong information. The correct one is here :
~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.7 (jessie) Release: 8.7 Codename: jessie
Apache 2.4.x and PHP 7.0.x
And latest error log :
[Thu Jul 19 11:30:09.003618 2018] [proxy_fcgi:error] [pid 21544:tid 140343206991616] [client 10.128.18.11:1604] AH01071: Got error 'PHP message: PHP Notice: Undefined index: new_thread in /var/www/ mibew.dwebsite.com/httpdocs/plugins/AARInnovations/Mibew/Plugin/TrayNotification/Plugin.php on line 117\n' [Thu Jul 19 11:30:18.977548 2018] [proxy_fcgi:error] [pid 21505:tid 140343022352128] [client 10.128.18.11:5085] AH01071: Got error 'PHP message: PHP Notice: Undefined index: new_thread in /var/www/ mibew.dwebsite.com/httpdocs/plugins/AARInnovations/Mibew/Plugin/TrayNotification/Plugin.php on line 117\n' [Thu Jul 19 11:30:28.980396 2018] [proxy_fcgi:error] [pid 21505:tid 140343114671872] [client 10.128.18.11:8829] AH01071: Got error 'PHP message: PHP Notice: Undefined index: new_thread in /var/www/ mibew.dwebsite.com/httpdocs/plugins/AARInnovations/Mibew/Plugin/TrayNotification/Plugin.php on line 117\n' [Thu Jul 19 11:30:36.456402 2018] [proxy_fcgi:error] [pid 21505:tid 140343131457280] [client 10.128.18.11:11762] AH01071: Got error 'PHP message: PHP Notice: Undefined index: new_thread in /var/www/ mibew.dwebsite.com/httpdocs/plugins/AARInnovations/Mibew/Plugin/TrayNotification/Plugin.php on line 117\n'
Thank you in advance for your input.
Nora
On Wed, Jul 18, 2018 at 4:38 PM Nora - rSchoolToday < nora.fuentes@rschooltoday.com> wrote:
Hi Fedor,
You are correct, it`s impossible to solve something that cannot be replicated. We will start by trying to enhance the PHP version. Thank you!
Nora
On Wed, Jul 18, 2018 at 12:18 PM Fedor A. Fetisov < notifications@github.com> wrote:
1.
It's impossible to solve the issue that one is unable to reproduce. 2.
Apache 2.2.x and PHP 5.2.x
Your PHP version is lower than required https://mibew.org/features#requirements (i.e. 5.4+). It's not necessary the reason for the issue, but it could be.
1.
No error log for mibew vhost.
Do you mean that there are no errors in the log, or that you're unable to access the log?
1.
Sorry, I do not know how to access developers console.
https://developers.google.com/web/tools/chrome-devtools/console/
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Mibew/mibew/issues/230#issuecomment-405968843, or mute the thread https://github.com/notifications/unsubscribe-auth/AIyvENEHs63Z-HBoFFUTRzXeKEkg0C5Jks5uH1HNgaJpZM4VRtsQ .
The warning messages has nothing to do with the core of Mibew Messenger. They produced by the third party plugin.
One should look after messages that are relevant to the issue in question. You know when the error occured and you have error logs, so you could try to determine the interconnection.
Since the problem occurs seldomly, I could only assume that it's a result of some special conditions (and probably related to a client environment).
Thank you, Fedor. Forwarding this information to our Sysadmins.
Have a great weekend!
Nora
On Thu, Jul 19, 2018 at 5:50 PM Fedor A. Fetisov notifications@github.com wrote:
1.
The warning messages has nothing to do with the core of Mibew Messenger. They produced by the third party plugin. 2.
One should look after messages that are relevant to the issue in question. You know when the error occured and you have error logs, so you could try to determine the interconnection. 3.
Since the problem occurs seldomly, I could only assume that it's a result of some special conditions (and probably related to a client environment).
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Mibew/mibew/issues/230#issuecomment-406410160, or mute the thread https://github.com/notifications/unsubscribe-auth/AIyvECZRvuGPlBzYlxqaXtj2EyB6ks2Hks5uIPEegaJpZM4VRtsQ .
Closed due to inactivity
Environment
Expected behavior
Visitors should be able to view our replies
Actual behavior
Visitors do not see our replies
Steps to reproduce the behavior
In this example client confirmed via phone, he was not able to view our replies. Why? https://www.screencast.com/t/58XEeHVqHCB Chat operator and client were both using Chrome. Thank you for any help you can provide.