*Need Help* Timeline Upload Items not working - "Missing Marka.JS.Map"

Kyle this seems like a setting problem of your server.

İt may be a permission problem or something like that.

Could you check the logs during the error happens, possibly there are clues there.

That's the problem there are no errors, just the one listed. I only know this error because it shows in my litespeed web server logs and only occurs when doing the multiple uploads on the comment posts or timeline feed posts. I can upload 1 image or item without a problem. Only run into issue with multiple. If it was a permission issue It would not show after I refresh and the 1 image would not work. Id also receive an error, which I am not. Atleast I think. This is all in the post. 

I am also on my own server but not having this problem.
can you do a tail -f /var/log/litespeed/error.log ( or however it iserror log filename).
may be it is passing very fast and not catched.

The tail is matching up with my error logs in Litespeed webserver. This was realtime as I was uploading photos. The kill is when I am refreshing page. 

Debug while waiting on screen images are uploaded to.  

well actually I couldnt understand the problem from these data ...

Yeah, everything is processing like it should. I did notice something though when doing logs, I had to restart the web server due to the logs stopped processing after my debug. The logs in panel for UNA have no errors updated since way back when I migrated and only log really growing is the profiler. Settings all look good and no errors makes it a pain. The only error that is consistent is the marka.js.map error. Maybe I need to setup a symlink 0.0 Not sure

Alex T⚜️ MariaDB does not use all the sections in that post, but what it does allow I do have. Most with InnoDB with Maria seems automatic. It would not take my old MySQL for the # of CPU's and Deadlocks. Here is my my.cnf : 

[mysqld]

innodb_log_file_size=400M

innodb_flush_method=O_DIRECT

innodb_io_capacity=1000

innodb_old_blocks_time=1000

innodb_open_files=5000

key_buffer_size=64M

read_buffer_size=256K

read_rnd_buffer_size=256K

query_cache_size=256M

query_cache_limit=5M

query_cache_type=on

join_buffer_size=4M

sort_buffer_size=4M

max_heap_table_size=128M

tmp_table_size=1024M

table_open_cache=100000

table_definition_cache=4000

thread_cache_size=192

collation-server=utf8mb4_unicode_ci

init-connect='SET NAMES utf8mb4'

character-set-server=utf8mb4

If you know of the options for Maria a may be missing please share. 

INNODB LogINNODB Variables Update looks like for rollback for timeout there is only an on and off, so as of now I got 

innodb_stats_on_metadata=on

innodb_log_file_size=400M

innodb_flush_method=O_DIRECT

innodb_io_capacity=1000

innodb_old_blocks_time=1000

innodb_open_files=5000

innodb_buffer_pool_size=4096M

innodb_lock_wait_timeout=4

innodb_rollback_on_timeout=on

Maybe delete the extra stuff you do not mention? The others were some things others have mentioned in the CyberPanel community. Sooo it looks like my issue was database related. Looks like some things are different with InnoDB in Maria. For example this one innodb_rollback_on_timeout=on and this line does not exist: binlog_format = MIXED and transaction_isolation = READ-COMMITTED so these were what was throwing off my My.CNF when I deleted the other options. I didn't have to change my pool_instances because mine is on 8 by default.   Please still do share if I should remove any of these.  GOSH Dangit, nevermind it didnt work :( I just give up. 

Alex T⚜️ here are my buffer variables and some others: 

 Autoextend increment    64

innodb_autoinc_lock_mode    1

innodb_background_scrub_data_check_interval    3600

innodb_background_scrub_data_compressed    OFF

innodb_background_scrub_data_interval    604800

innodb_background_scrub_data_uncompressed    OFF

innodb_buf_dump_status_frequency    0

innodb_buffer_pool_dump_at_shutdown    OFF

innodb_buffer_pool_dump_now    OFF

innodb_buffer_pool_dump_pct    100

innodb_buffer_pool_filename    ib_buffer_pool

innodb_buffer_pool_instances    8

innodb_buffer_pool_load_abort    OFF

innodb_buffer_pool_load_at_startup    OFF

innodb_buffer_pool_load_now    OFF

innodb_buffer_pool_populate    OFF

    Buffer pool size    4,096 MiB

innodb_change_buffer_max_size    25

innodb_ft_max_token_size    84

innodb_ft_min_token_size    3

innodb_ft_num_word_optimize    2000

innodb_ft_result_cache_limit    2000000000

innodb_ft_server_stopword_table    

innodb_ft_sort_pll_degree    2

innodb_ft_total_cache_size    640000000

innodb_ft_user_stopword_table    

innodb_idle_flush_pct    100

innodb_immediate_scrub_data_uncompressed    OFF

innodb_instrument_semaphores    OFF

innodb_io_capacity    1000

innodb_io_capacity_max    2000

innodb_kill_idle_transaction    0

innodb_large_prefix    OFF

innodb_lock_schedule_algorithm    fcfs

innodb_lock_wait_timeout    4

innodb_locking_fake_changes    ON

innodb_locks_unsafe_for_binlog    OFF

innodb_log_arch_dir    ./

innodb_log_arch_expire_sec    0

innodb_log_archive    OFF

innodb_log_block_size    512

innodb_log_buffer_size    16,384 KiB

innodb_log_checksum_algorithm    INNODB

innodb_log_compressed_pages    ON

innodb_log_file_size    410 k KiB

innodb_log_files_in_group    2

innodb_log_group_home_dir    ./

See Last Post that has my current InnoDB directives for variables. I am wondering if it could be my flushing option, not sure. So I got my other variable settings to work and deleted the ones I got elsewhere :/ testing now. So with just 

innodb_stats_on_metadata=off

innodb_log_file_size=400M

innodb_buffer_pool_size=4096M

innodb_lock_wait_timeout=4

innodb_rollback_on_timeout=on

transaction-isolation=READ-COMMITTED

binlog_format=MIXED

and clearing cache. this did not work. Yes before someone hops in and says so and hops out, I restarted Maria and Web Server, each time i made a change. I did from studio and from with the the web directory. Keep in mind Jquery is necessary when it comes to loading multiple images. Its not like they are not there. They upload, but do not show unless you refresh the page and then you have to post then refresh again. This also only happens when it is more then one image. Litespeed logs and bxprofiler show that the file is uploading without error.  I really do not think this is a database issue and there are no errors which has me in a loop, and it might very well be. All INNODB settings at this point unless something looks off in those variables, is as it should be based on what can be found here.  There are some extra InnoDB variables didnt see with my old MySQL when I was on Cpanel. What is so frustrating is for a moment I was able to do it and then not again. So it could still be database, but I cant be sure. At this point I am beyond frustration 🙀 

We also have a similar situation on our website: Linguria.com We have to refresh the page after uploading an image to timeline. And, if we upload multiple images it may take 4 - 5 minutes to process all images. 

Thank you LeonidS 

Yeah anywhere you get the fields to upload the images. Everything else is fine. Before I moved over from Cpanel never had this issue. So I am sure it is something that is missing or not being read right. Still cant figure it out through my troubleshooting so hope someone can help us. 

That is exactly what I use for our homepage. Keep in mind the content uploads, it shows, but only after refreshing. This one happens with two or more photos and you refresh they show and then hit post and then refresh again and they show. This issue is with all areas that you can post to and attach content. What I do not understand is this issue was not present prior. So for me I find it hard to believe it will be fixed, but maybe I will be proven wrong. Before I moved this over we ran an event that made it so people had to upload multiple images to a timeline post in an event telling a story for a contest. It worked as intended. No longer there now since my timeline reinstall of course. The thing is I never tried posting new items since conversion so never noticed it was not working anymore until the day I asked for help. So unsure if this could have happened the day we reinstalled or from the beginning of conversion all together. So at a standstill at this time. Quick update to this *I tried all things emoticons, links, and Videos, and none of those have this issue only images.* I also tried without GD being I have imagemagick on back end and with GD library. We tried disabling caches. 

Figured Id share this to in case this helps. Keep in mind this is my MYQL in a whole for buffering, but the main site is the social community: Also UNA shows I am on MYSQL5.5.5, but I am on Maria DB is this an issue? 

Percona-XtraDB, Supports transactions, row-level locking, foreign keys and encryption for tables

[ Variables | Buffer Pool | InnoDB Status ]

Buffer Pool Usage

Total : 262,136 pages / 4,096 MiB

Free pages    257,917

Dirty pages    0

Pages containing data    4,198

Pages to be flushed    3,567

Busy pages    21

Buffer Pool Activity

Read requests    521,658

Write requests    26,799

Read misses    4,055

Write waits    0

Read misses in %    777.33 m %

Write waits in %    0 %

I also noticed that If you use the multi uploader  just uploading one at a time they will show without issues. So most definitely only when two or more images are uploaded together.  Alex T⚜️ 

Sighs 😫 Please read my posts. Yes all this is set in my header inc and yes this is the engine it is set to. Nothing has changed in my conversion. You already sent me to this post. Every simple answer has already been dealt with or not an issue. This is far more than that. My site is live, it is running, it is reading and writing, just not multiple image uploads. You can use the multi uploader and do one at a time, but not 2 or 3 at a time without refreshing after. There are no errors to help troubleshoot. Only reason I am mentioning the database is because you brought it up so I checked it out. This has not resolved the issue unless MariaDB has extra options that need to be set for INNODB. I have shared all my findings in this post and what I have tried. I have already troubleshooted with Leonid S and he was unable to figure it out neither and referred it to you. I need real help.

Kyle i am using Mariadb too without any problems.

Can it be PHP max post size setting? How much is it in your server?

It is in this post already, everything is in this post.  All my stuff is set high and I can uplaod videos, etc without a problem. Mine is set at 512. https://vybz.live/php.php  

At this point, what I am going to do is try to convert over to Aria. Maybe it is an issue with InnoDB in connection with MariaDB in relation to UNA. If this does not resolve issue at this point it has to be something else. I wish I tested this before I reinstalled the timeline. It could very much be related to that, but now I will never know. Keep in mind guys everything was converted over to CyberPanel from Cpanel with same settings. Nothing has changed and it worked before. Only things that have changed are for example MariaDB instead of MySQL because CyberPanel is built on it. Also Litespeed uses LSPHP but same concept and everything is set really high there is no way at this point between switchign between different PHP version that PHP is the issue. I do feel it may be database related being it worked for a split second when I changed my Innodb settings in the My.CNF. So to I am going to try to convert database. Hopefully by the time Una evolves and does end up using transactions Aria will support it to. 

İ had many problems with php7.2 and .3 and using 7.1 now, did you try with different PHP versions?

Yes 

İ don't think that it's related to Mariadb as i am using from the beginning without any problem.

But better to test.

Finally!!!!! Somehow I always end up fixing it my own way. So changing to Aria has resolved the issue. There has to be an INNODB option that cause an issue but not sure at this time. Everything was the same though. At the time I will stick with Aria. Keep in mind trying Alex's fix for #INNODB for #MySQL did not work on #MariaDB for me. I would advise at this point unless tested and a resolution, do not use INNODB, but use #MyISAM or #Aria engines instead if you use MariaDB. If you have a fix please share.