Bonjour,
Je viens d'installer SquashTM V4.0.0 avec Postgresql 14 sur Ubuntu 22. Toute marche bien sauf les pièces jointes. Dans les paramètres système, la taille maximum est 2 MB. Mais seulement les fichiers moins de 10 KB sont acceptés. Dans tous les autres cas, je reçois une erreur générique sans détails. J'ai essayé de regarder les logs Postgresql et squash mais ça dit rien concernant cette erreur. Je n'ai pas cette erreur par contre si j'installe sur Windows 10.
Est-ce-que vous avez des idées de quels paramètres (squash ou même Ubuntu) cause ce problème?
Merci,
Andrew
Erreur téléversée pièces jointes plus gros que 10 KB
-
- Messages : 2
- Inscription : ven. sept. 02, 2022 3:50 pm
-
- Messages : 3
- Inscription : jeu. sept. 24, 2020 1:38 pm
Re: Erreur téléversée pièces jointes plus gros que 10 KB
Bonjour Andrew,
J'ai tenté de faire une monté de version vers la version 4.0.0 sur ma plateforme Ubuntu 22.04 et une base de données maria dB mais je n'arrive pas à lancer le service squash-tm. Les logs de de squash-tm et d'apache2, ne permettent pas d'identifier l'origine du problème. Pas plus que les messages d'erreur affichés dans le résultat de la commande de lancement du service, présenté ci-dessous :
-°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°-
squash-tm.service - Squash-tm daemon
Loaded: loaded (/etc/systemd/system/squash-tm.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2022-09-09 15:34:43 CEST; 4 days ago
Main PID: 1135019 (code=exited, status=1/FAILURE)
CPU: 20.164s
sept. 09 15:34:43 billfoster-HP-EliteBook-840-G1 systemd[1]: squash-tm.service: Scheduled restart job, restart counter is at 4.
sept. 09 15:34:43 billfoster-HP-EliteBook-840-G1 systemd[1]: Stopped Squash-tm daemon.
sept. 09 15:34:43 billfoster-HP-EliteBook-840-G1 systemd[1]: squash-tm.service: Consumed 20.164s CPU time.
sept. 09 15:34:43 billfoster-HP-EliteBook-840-G1 systemd[1]: squash-tm.service: Start request repeated too quickly.
sept. 09 15:34:43 billfoster-HP-EliteBook-840-G1 systemd[1]: squash-tm.service: Failed with result 'exit-code'.
sept. 09 15:34:43 billfoster-HP-EliteBook-840-G1 systemd[1]: Failed to start Squash-tm daemon.
-°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°-
Avez-vous été confronté à ce type de problème ?
Merci de votre aide
FosterBill
J'ai tenté de faire une monté de version vers la version 4.0.0 sur ma plateforme Ubuntu 22.04 et une base de données maria dB mais je n'arrive pas à lancer le service squash-tm. Les logs de de squash-tm et d'apache2, ne permettent pas d'identifier l'origine du problème. Pas plus que les messages d'erreur affichés dans le résultat de la commande de lancement du service, présenté ci-dessous :
-°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°-
squash-tm.service - Squash-tm daemon
Loaded: loaded (/etc/systemd/system/squash-tm.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2022-09-09 15:34:43 CEST; 4 days ago
Main PID: 1135019 (code=exited, status=1/FAILURE)
CPU: 20.164s
sept. 09 15:34:43 billfoster-HP-EliteBook-840-G1 systemd[1]: squash-tm.service: Scheduled restart job, restart counter is at 4.
sept. 09 15:34:43 billfoster-HP-EliteBook-840-G1 systemd[1]: Stopped Squash-tm daemon.
sept. 09 15:34:43 billfoster-HP-EliteBook-840-G1 systemd[1]: squash-tm.service: Consumed 20.164s CPU time.
sept. 09 15:34:43 billfoster-HP-EliteBook-840-G1 systemd[1]: squash-tm.service: Start request repeated too quickly.
sept. 09 15:34:43 billfoster-HP-EliteBook-840-G1 systemd[1]: squash-tm.service: Failed with result 'exit-code'.
sept. 09 15:34:43 billfoster-HP-EliteBook-840-G1 systemd[1]: Failed to start Squash-tm daemon.
-°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°--°-°-°-°-°-°-°-°-
Avez-vous été confronté à ce type de problème ?
Merci de votre aide
FosterBill
Re: Erreur téléversée pièces jointes plus gros que 10 KB
Hello,
Do you have any logs on 'logs' folder on squash-tm ? If logs are not precise can you try to put them on debug : https://tm-en.doc.squashtest.com/v4/ins ... logs-level and try again to restart.
Did you update your squash database as requested on documentation : https://tm-en.doc.squashtest.com/v4/ins ... version-40 ?
Regards,
Yamina
Do you have any logs on 'logs' folder on squash-tm ? If logs are not precise can you try to put them on debug : https://tm-en.doc.squashtest.com/v4/ins ... logs-level and try again to restart.
Did you update your squash database as requested on documentation : https://tm-en.doc.squashtest.com/v4/ins ... version-40 ?
Regards,
Yamina
-
- Messages : 2
- Inscription : ven. sept. 02, 2022 3:50 pm
Re: Erreur téléversée pièces jointes plus gros que 10 KB
So, in a weird twist, running as a linux service doesn't write into the log at all.Yamina a écrit : ↑jeu. sept. 15, 2022 11:05 am Hello,
Do you have any logs on 'logs' folder on squash-tm ? If logs are not precise can you try to put them on debug : https://tm-en.doc.squashtest.com/v4/ins ... logs-level and try again to restart.
Did you update your squash database as requested on documentation : https://tm-en.doc.squashtest.com/v4/ins ... version-40 ?
Regards,
Yamina
If I instead start it manually using startup.sh (command: nohup ./startup.sh &), it suddenly writes to the log and the 10KB upload restriction is gone.
I'm using the same service file as suggested in the docs
[Unit]
Description=Squash-TM daemon
After=systemd-user-sessions.service time-sync.target
[Service]
WorkingDirectory=/opt/squash-tm/bin
ExecStart=/opt/squash-tm/bin/startup.sh
ExecStop=/bin/kill $MAINPID
KillMode=process
Type=simple
#Restart=on-failure
User=squash-tm
Group=squash-tm
[Install]
WantedBy=multi-user.target
This makes even less sense to me now.
Dernière modification par andrew_squash le jeu. sept. 15, 2022 9:44 pm, modifié 2 fois.
-
- Messages : 2
- Inscription : ven. sept. 02, 2022 3:50 pm
Re: Erreur téléversée pièces jointes plus gros que 10 KB
Nevermind, I just realized my mistake. The service is running under user squash-tm where as if I run manually it's using my other user.
I must have run this command chown -R squash-tm: /opt/squash-tm/ the first time without sudo (as Ubuntu won't throw an error for chmod even if it is rejected in the terminal). Frankly I'm surprised it ran that well at all originally.
I must have run this command chown -R squash-tm: /opt/squash-tm/ the first time without sudo (as Ubuntu won't throw an error for chmod even if it is rejected in the terminal). Frankly I'm surprised it ran that well at all originally.
Re: Erreur téléversée pièces jointes plus gros que 10 KB
Hello,
regarding the attachment upload issue, do you have a web server in front of squash-tm ?
If so, please check the max upload size and max post body size in your web server configuration (the exact names of these parameters depend upon which webserver is used, ie nginx, apache, etc.). Also check your webserver logfiles for the error.
regarding the attachment upload issue, do you have a web server in front of squash-tm ?
If so, please check the max upload size and max post body size in your web server configuration (the exact names of these parameters depend upon which webserver is used, ie nginx, apache, etc.). Also check your webserver logfiles for the error.
Re: Erreur téléversée pièces jointes plus gros que 10 KB
If so, kindly verify that your web server configuration allows for both the maximum upload and post body sizes.andrew_squash a écrit : ↑jeu. sept. 15, 2022 10:09 pm Nevermind, I just realized my mistake. The service is running under user squash-tm where as if I run manually it's using my other user.
I must have run this command chown -R squash-tm: /opt/squash-tm/ the first time without sudo (as Ubuntu won't throw an error for chmod even if it is rejected in the terminal). Frankly I'm surprised it ran that well at all originally. run 3