Closed hsninbil closed 5 years ago
This very uninformative error is the result of an empty ajax answer. This means that the call crashed, usually on a database error. It very much depends on your set-up where you can find that error... maybe journalctl?
I cannot help you with that error message, and info about which OS and Taranis version you are using.
Hi, thank you. about the version ---for my OS is : Linux taranis-virtual-machine 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (ubuntu 18.4Lts). ----Taranis is Taranis version 3.4.4
------------------------ outcomes journalctl Logs begin at Thu 2019-01-17 21:45:19 EST, end at Mon 2019-01-21 14:01:32 EST. -- Jan 17 21:45:19 taranis-virtual-machine kernel: Linux version 4.15.0-29-generic (buildd@lgw01-amd64-057) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC Jan 17 21:45:19 taranis-virtual-machine kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=6a9c4cd1-a037-4078-8569-1e7c6033ba22 ro quiet splash Jan 17 21:45:19 taranis-virtual-machine kernel: KERNEL supported cpus: Jan 17 21:45:19 taranis-virtual-machine kernel: Intel GenuineIntel Jan 17 21:45:19 taranis-virtual-machine kernel: AMD AuthenticAMD Jan 17 21:45:19 taranis-virtual-machine kernel: Centaur CentaurHauls Jan 17 21:45:19 taranis-virtual-machine kernel: Disabled fast string operations Jan 17 21:45:19 taranis-virtual-machine kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Jan 17 21:45:19 taranis-virtual-machine kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Jan 17 21:45:19 taranis-virtual-machine kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Jan 17 21:45:19 taranis-virtual-machine kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' Jan 17 21:45:19 taranis-virtual-machine kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' Jan 17 21:45:19 taranis-virtual-machine kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Jan 17 21:45:19 taranis-virtual-machine kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 Jan 17 21:45:19 taranis-virtual-machine kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 Jan 17 21:45:19 taranis-virtual-machine kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. Jan 17 21:45:19 taranis-virtual-machine kernel: e820: BIOS-provided physical RAM map: Jan 17 21:45:19 taranis-virtual-machine kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009e7ff] usable Jan 17 21:45:19 taranis-virtual-machine kernel: BIOS-e820: [mem 0x000000000009e800-0x000000000009ffff] reserved Jan 17 21:45:19 taranis-virtual-machine kernel: BIOS-e820: [mem 0x00000000000dc000-0x00000000000fffff] reserved Jan 17 21:45:19 taranis-virtual-machine kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bfedffff] usable Jan 17 21:45:19 taranis-virtual-machine kernel: BIOS-e820: [mem 0x00000000bfee0000-0x00000000bfefefff] ACPI data Jan 17 21:45:19 taranis-virtual-machine kernel: BIOS-e820: [mem 0x00000000bfeff000-0x00000000bfefffff] ACPI NVS Jan 17 21:45:19 taranis-virtual-machine kernel: BIOS-e820: [mem 0x00000000bff00000-0x00000000bfffffff] usable Jan 17 21:45:19 taranis-virtual-machine kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved Jan 17 21:45:19 taranis-virtual-machine kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved Jan 17 21:45:19 taranis-virtual-machine kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved Jan 17 21:45:19 taranis-virtual-machine kernel: BIOS-e820: [mem 0x00000000fffe0000-0x00000000ffffffff] reserved Jan 17 21:45:19 taranis-virtual-machine kernel: BIOS-e820: [mem 0x0000000100000000-0x000000013b7fffff] usable Jan 17 21:45:19 taranis-virtual-machine kernel: NX (Execute Disable) protection: active Jan 17 21:45:19 taranis-virtual-machine kernel: SMBIOS 2.7 present. Jan 17 21:45:19 taranis-virtual-machine kernel: DMI: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 05/19/2017 Jan 17 21:45:19 taranis-virtual-machine kernel: Hypervisor detected: VMware Jan 17 21:45:19 taranis-virtual-machine kernel: vmware: TSC freq read from hypervisor : 2808.005 MHz Jan 17 21:45:19 taranis-virtual-machine kernel: vmware: Host bus clock speed read from hypervisor : 66000000 Hz Jan 17 21:45:19 taranis-virtual-machine kernel: vmware: using sched offset of 13360748787 ns Jan 17 21:45:19 taranis-virtual-machine kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Jan 17 21:45:19 taranis-virtual-machine kernel: e820: remove [mem 0x000a0000-0x000fffff] usable Jan 17 21:45:19 taranis-virtual-machine kernel: e820: last_pfn = 0x13b800 max_arch_pfn = 0x400000000 Jan 17 21:45:19 taranis-virtual-machine kernel: MTRR default type: uncachable Jan 17 21:45:19 taranis-virtual-machine kernel: MTRR fixed ranges enabled: Jan 17 21:45:19 taranis-virtual-machine kernel: 00000-9FFFF write-back Jan 17 21:45:19 taranis-virtual-machine kernel: A0000-BFFFF uncachable Jan 17 21:45:19 taranis-virtual-machine kernel: C0000-CFFFF write-protect Jan 17 21:45:19 taranis-virtual-machine kernel: D0000-EFFFF uncachable Jan 17 21:45:19 taranis-virtual-machine kernel: F0000-FFFFF write-protect Jan 17 21:45:19 taranis-virtual-machine kernel: MTRR variable ranges enabled: Jan 17 21:45:19 taranis-virtual-machine kernel: 0 base 000C0000000 mask 7FFC0000000 uncachable
--- for my OS is: ubuntu 18.4LTS --- Taranis version 3.4.4
------------------------ outcomes journalctl
This does contain the database error; just a part of the boot log. The log lines to need to find start with 'AJAX ERROR'
It may be found with "journalctl -e" or in some /var/log/* file.
I also have a guess on the issue at hand. In 3.5.0 (released this weekend) we fix a bug when you add an individual when there are no individual roles defined in your system yet. Can you check this? -- success, MarkOv
Mark Overmeer MSc MARKOV Solutions
Mark@Overmeer.net solutions@overmeer.net
Dear MarkOv, you will find as attached taranis logs and the result with 'Journalctl -e'.
Best regards journal-e-taranis-txt.txt
Your journalctl output clearly states:
==> STMNT: INSERT INTO constituent_individual ( call247, call_hh, emailaddress, firstname,
lastname, role, status, tel_mobile, tel_regular) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ? )
==> BINDS: 1 1 hasni.nbl@gmail.com Nabil hosni 0 5555555555
Jan 21 23:50:33 taranis-virtual-machine TARANIS[1017]: DBD::Pg::st execute failed: ERROR:
invalid input syntax for integer: "" at /home/taranis/taranis-3.4.4/perl5/Taranis/Database.pm line 214.
The only blank BIND is between 'hosni' and '0': two blanks in a row if you look carefully. In the query (STMNT) that is on the place of the 'role' parameter. So, this confirms my guess of 11 hours ago (see above) that you do not yet have defined an 'constituent individual role' in your system. This old bug has been fixed in 3.5.0
(Be careful with posting logs to this public issue list: that may contain too much information about your system. Please be selective to send only the lines which are important to support your question)
Dear Markov, Firstly, Thank you. I will plan to upgrade Taranis system to new version 3.5. moreover, i would ask about the limit in the publication and maillist (max number to newsletter, advisories, email daily, for sending with taranis.).
Dear,
please can you help me? When sending an email, this error message appeared :
Hamburgers! The cornerstone of any nutritious breakfast. [parsererror - SyntaxError: Unexpected end of JSON input (200)]
...anyways, check logs for details!
Ajax call for /taranis/load/assess/mail/mailItem
Please do not use email style in github issues.
As your quote says: "...anyways, check logs for details!" The message you see is a generic crash; the reason can be found in one of the logs (where depends on your OS configuration) Without additional information, I am unable to help.
Hi, the issue arrives in creating a New Constitution Individual, the below message:
Error Message in taranis system : None shall pass! [parsererror - SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data (200)] ...anyways, check logs for details! Ajax call for /taranis/load/configuration/constituent_individuals/saveNewConstituentIndividual