Hello world!

hallo, this is supposedly my technical blog. probably a junk for you, but i put it necessarily for me since i’m bad at remembering things…

so i write this just as sort of my journal of the technical problem i’ve experienced, in case i stumble upon the same problem in the future.

Viewing system log in rocky linux 9

It happens when you have application that suddenly throw error and you don’t have the the app generated log, or the error is not from inside of the app.
One way to check is by using this command:

dmesg -T | grep mariadb

the above is the example of finding system error regarded of process named “mariadb” . Since it using grep command in means all log string that contained string or substring “mariadb” will be shown.

This command really useful to track error like suddenly stopped service, like from the result of the command:

[Sat Jan 4 01:02:33 2025] mariadbd invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0

[Sat Jan 4 01:02:33 2025] CPU: 7 PID: 5430 Comm: mariadbd Kdump: loaded Not tainted 5.14.0-427.26.1.el9_4.x86_64 #1

[Sat Jan 4 01:02:33 2025] [ 1112] 990 1112 36666767 25232594 221720576 2045536 0 mariadbd

[Sat Jan 4 01:02:33 2025] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/mariadb.service,task=mariadbd,pid=1112,uid=990

[Sat Jan 4 01:02:33 2025] Out of memory: Killed process 1112 (mariadbd) total-vm:146667068kB, anon-rss:100930208kB, file-rss:168kB, shmem-rss:0kB, UID:990 pgtables:216524kB oom_score_adj:0

[Sat Jan 4 01:02:36 2025] oom_reaper: reaped process 1112 (mariadbd), now anon-rss:436kB, file-rss:40kB, shmem-rss:0kB

As you can see above, we are told that service of mariadbd was killed because of out of memory error, thus we can do the fixing to enlarge the memory or optimizing the process that run before the service was killed.

dbeaver error when connecting to postgresql

so i happened to experience error when trying to connect to postgresql via dbeaver.

after lurking on the internet there are three steps need to do:

  • install jdbc driver for postgresql here https://jdbc.postgresql.org/
  • check if java already installed:
    by opening command prompt and type this:

where java

if error then java is not installed, you need to install java.

  • after that then you need to copy the ca sertificate from java to dbeaver installation directory.
    from java installation go to lib/security folder, there you’ll see cacert file, copy and paste it to the same lib/security inside dbeaver installation folder, just overwrite the current cacerts file.
  • then go to dbeaver installation folder llok for dbeaver.ini file, erase this line:

-Djavax.net.ssl.trustStoreType=WINDOWS-ROOT

try closing the dbeaver apps if open, the try opening the app again and try to connect to progresql db, it should be working right now and auto download necesary files.

samba error: “session setup failed: NT_STATUS_LOGON_FAILURE” when adding new user

it really strange when i use samba for the first time this error not happened.

but when i add new user to share samba it didn’t work, it continue to produce “session setup failed: NT_STATUS_LOGON_FAILURE”

i tried both using straight connection smb://server/sharename or by smbclient connection.

this error because of failed connection LAN/hosts problem, wrong user name or password, or because of not adding domain name/workgroup (if you tried to connect to windows share).

it turn out my problem is that the password from linux password is not synced with samba password, so you need to add it using the command:

Continue reading

Installing BI Publisher in windows 64 bit with office 32 bit

Now with the new program we are upgrading our system to a new one, from oracle 8i+dev 6i to the latest oracle db 12c + dev 11g/10g.

in my system: 64bit windows 8.1, office 2013 32 bit.

**Installing BI Publisher.

there are some notes in regard of program installations:
– the bit version of java must be the same with the bit version of BI publisher, if it is 32bit then all 32bit.

– the BI bit version must be the same with the office version, if office is 32 bit then the BI publisher must also a 32bit version, even though the system is 64bit.

– since BI somehow unable to detect the java installation, since they check in wrong registry folder -duh-… so you must export and import the registry setting.
1) first open registry, look for HKLM\SOFTWARE\WOW6432\JavaSoft\Java Runtime Environment 2) export the registry.
3) open the exported registry using a notepad.
4) remove WOW6432\ so the lines should be: HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment. 5) save the file and import it back to the registry.
6) start installing BI Publisher.

– now is that enough? not yet, since when you open the office program, it will only show the manual, but not the BI tab. Now the step is for you to enter the installation folder of the BI Publisher.
if you not change anything, the default installation folder is: Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\DotnetInstallfiles. – there you just need to run the setup file.
– now open the the office program, the BI tabs should be there.

jardiknas.kemdiknas.go.id/?url=

I don’t know what’s wrong with our ISP today.
first my lintas arta ISP forcing us to use their DNS server which – with all due respect – is crap, it has no stability, several times a day the dns is not working (failed to resolve domain names), the alternative is by using nawala dns 180.131.144.144 and 180.131.145.145, at least this one is stable.

Continue reading

Jperf point to point network connection diagnostic

This tool here iperf or jperf, is the one I find very useful in measuring the speed and reliability of a connection either in LAN or through internet/WAN.
and it is cross platform since it is made using java, you just need to install it in each points you want to test, and one or some of them act as server while the rest as client. Continue reading

BSOD STOP: 0x0000007B when installing windows

When installing windows xp or 2003 server, sometimes we encounter this BSOD:
STOP: 0x0000007B (0xF78D2524,0xC0000034,0x00000000,0x00000000)
right before the installation detecting the harddisk.
the 7B error indicate driver error, while (0xF78D2524,0xC0000034,0x00000000,0x00000000) indicate specific error, which is HDD problem in related to BIOS SATA configuration. Continue reading