Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • dumux dumux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 109
    • Issues 109
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 103
    • Merge requests 103
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • dumux-repositoriesdumux-repositories
  • dumuxdumux
  • Issues
  • #994

dumux listens on TCP-Ports

Having opened TCP ports which are not needed is a security risk. A possible attack can be to inject buffers with arbitrary content. So this should not happen if not otherwise configured. The ports are open on all IPv4-Adresses. I see currently two jobs on hal which have opened TCP Ports 1027 and 1028 for whatever reasons:

root@hal:/var/log# lsof  -nP -iTCP -sTCP:LISTEN  |grep 1027
test_pnm_ 608139 maziar   15u  IPv4 2121895      0t0  TCP *:1027 (LISTEN)
root@hal:/var/log# lsof  -nP -iTCP -sTCP:LISTEN  |grep 1028
test_darc 771895  nepal   16u  IPv4 2944280      0t0  TCP *:1028 (LISTEN)

Process of maziar looks in tool pstree -u

slurm_script(608134)───mpirun(608135)─┬─test_pnm_drop_s(608139)─┬─{test_pnm_drop_s}(608140)
                                      │                         └─{test_pnm_drop_s}(608141)
                                      ├─{mpirun}(608136)
                                      ├─{mpirun}(608137)
                                      └─{mpirun}(608138)

And with ps auxww | grep 608139

maziar    608139 98.8  9.7 11601160 6429192 ?    Rl   Feb18 7995:05 ./test_pnm_drop_stokes_1p

Process of nepal looks like:

root@hal:/var/log# pstree -u nepal -p 
slurm_script(771894)───test_darcy(771895)─┬─orted(771896)─┬─{orted}(771897)
                                          │               ├─{orted}(771898)
                                          │               └─{orted}(771899)
                                          ├─{test_darcy}(771900)
                                          └─{test_darcy}(771901)
root@hal:/var/log# ps auxww |grep 771895
nepal     771895 99.9  0.0 238064 29196 ?        Rl   Feb22 2154:57 ./test_darcy test_darcy.input

It would be interesting to stop this and/or document at least its cause. I have no idea of cause, it can be openmpi related but other things might be possible.

Edited Feb 24, 2021 by David Werner
Assignee
Assign to
Time tracking